 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| 2514j?avr?12/03 features high performance, low power avr ? 8-bit microcontroller advanced risc architecture ? 130 powerful instructions ? most single clock cycle execution ? 32 x 8 general purpose working registers ? fully static operation ? up to 16 mips throughput at 16 mhz ? on-chip 2-cycle multiplier non-volatile program and data memories ? 16k bytes of in-system self-programmable flash endurance: 10,000 write/erase cycles ? optional boot code section with independent lock bits in-system programming by on-chip boot program true read-while-write operation ? 512 bytes eeprom endurance: 100,000 write/erase cycles ? 1k byte internal sram ? programming lock for software security jtag (ieee std. 1149.1 compliant) interface ? boundary-scan capabilities according to the jtag standard ? extensive on-chip debug support ? programming of flash, eeprom, fuses, and lock bits through the jtag interface peripheral features ? 4 x 25 segment lcd driver ? two 8-bit timer/counters with separate prescaler and compare mode ? one 16-bit timer/counter with separate prescaler, compare mode, and capture mode ? real time counter with separate oscillator ? four pwm channels ? 8-channel, 10-bit adc ? programmable serial usart ? master/slave spi serial interface ? universal serial interface with start condition detector ? programmable watchdog timer with separate on-chip oscillator ? on-chip analog comparator ? interrupt and wake-up on pin change special microcontroller features ? power-on reset and programmable brown-out detection ? internal calibrated oscillator ? external and internal interrupt sources ? five sleep modes: idle, adc noise reduction, power-save, power-down, and standby i/o and packages ? 53 programmable i/o lines ? 64-lead tqfp and 64-pad mlf operating voltage: ? 1.8 - 5.5v for atmega169v ? 2.7 - 5.5v for atmega169l ? 4.5 - 5.5v for atmega169 temperature range: ? -40c to 85c industrial 8-bit microcontroller with 16k bytes in-system programmable flash atmega169v atmega169l atmega169 preliminary
2 atmega169v/l 2514j?avr?12/03 features (continued) speed grade: ? 0 - 1 mhz for atmega169v ? 0 - 8 mhz for atmega169l ? 0 - 16 mhz for atmega169 ultra-low power consumption ? active mode: 1 mhz, 1.8v: 400a 32 khz, 1.8v: 20a (including oscillator) 32 khz, 1.8v: 40a (including oscillator and lcd) ? power-down mode: 0.5a at 1.8v pin configurations figure 1. pinout atmega169 disclaimer typical values contained in this datasheet are based on simulations and characteriza- tion of other avr microcontrollers manufactured on the same process technology. min and max values will be available after the device is characterized. pc0 (seg12) vcc gnd pf0 (adc0) pf7 (adc7/tdi) pf1 (adc1) pf2 (adc2) pf3 (adc3) pf4 (adc4/tck) pf5 (adc5/tms) pf6 (adc6/tdo) aref gnd avcc 17 61 60 18 59 20 58 19 21 57 22 56 23 55 24 54 25 53 26 52 27 51 29 28 50 49 32 31 30 (rxd/pcint0) pe0 (txd/pcint1) pe1 lcdcap (xck/ain0/pcint2) pe2 (ain1/pcint3) pe3 (usck/scl/pcint4) pe4 (di/sda/pcint5) pe5 (do/pcint6) pe6 (clko/pcint7) pe7 (ss/pcint8) pb0 (sck/pcint9) pb1 (mosi/pcint10) pb2 (miso/pcint11) pb3 (oc0a/pcint12) pb4 (oc2a/pcint15) pb7 (t1/seg24) pg3 (oc1b/pcint14) pb6 (t0/seg23) pg4 (oc1a/pcint13) pb5 pc1 (seg11) pg0 (seg14) (seg15) pd7 pc2 (seg10) pc3 (seg9) pc4 (seg8) pc5 (seg7) pc6 (seg6) pc7 (seg5) pa7 (seg3) pg2 (seg4) pa6 (seg2) pa5 (seg1) pa4 (seg0) pa3 (com3) pa0 (com0) pa1 (com1) pa2 (com2) pg1 (seg13) (seg16) pd6 (seg17) pd5 (seg18) pd4 (seg19) pd3 (seg20) pd2 (int0/seg21) pd1 (icp1/seg22) pd0 (tosc1) xtal1 (tosc2) xtal2 reset gnd vcc atmega169 index corner 2 3 1 4 5 6 7 8 9 10 11 12 13 14 16 15 64 63 62 47 46 48 45 44 43 42 41 40 39 38 37 36 35 33 34 3 atmega169v/l 2514j?avr?12/03 overview the atmega169 is a low-power cmos 8-bit microcontroller based on the avr enhanced risc architecture. by executing powerful instructions in a single clock cycle, the atmega169 achieves throughputs approaching 1 mips per mhz allowing the system designer to optimize power consumption versus processing speed. block diagram figure 2. block diagram program counter internal oscillator watchdog timer stack pointer program flash mcu control register sram general purpose registers instruction register timer/ counters instruction decoder data dir. reg. portb data dir. reg. porte data dir. reg. porta data dir. reg. portd data register portb data register porte data register porta data register portd timing and control oscillator interrupt unit eeprom spi usart status register z y x alu portb drivers porte drivers porta drivers portf drivers portd drivers portc drivers pb0 - pb7 pe0 - pe7 pa0 - pa7 pf0 - pf7 vcc gnd aref xtal1 xtal2 control lines + - analog comp ara tor pc0 - pc7 8-bit data bus reset avcc calib. osc data dir. reg. portc data register portc on-chip debug jtag tap programming logic boundary- scan data dir. reg. portf data register portf adc pd0 - pd7 data dir. reg. portg data reg. portg portg drivers pg0 - pg4 universal serial interface avr cpu lcd controller/ driver 4 atmega169v/l 2514j?avr?12/03 the avr core combines a rich instruction set with 32 general purpose working registers. all the 32 registers are directly connected to the arithmetic logic unit (alu), allowing two independent registers to be accessed in one single instruction executed in one clock cycle. the resulting architecture is more code efficient while achieving throughputs up to ten times faster than conventional cisc microcontrollers. the atmega169 provides the following features: 16k bytes of in-system programmable flash with read-while-write capabilities, 512 bytes eeprom, 1k byte sram, 53 general purpose i/o lines, 32 general purpose working registers, a jtag interface for boundary-scan, on-chip debugging support and programming, a complete on-chip lcd controller with internal step-up voltage, three flexible timer/counters with compare modes, internal and external interrupts, a serial programmable usart, universal serial interface with start condition detector, an 8-channel, 10-bit adc, a programmable watchdog timer with internal oscillator, an spi serial port, and five software selectable power saving modes. the idle mode stops the cpu while allowing the sram, timer/counters, spi port, and interrupt syst em to continue functioning. the power- down mode saves the register contents but freezes the oscillator, disabling all other chip functions until the next interrupt or hardware reset. in power-save mode, the asyn- chronous timer and the lcd controller continues to run, allowing the user to maintain a timer base and operate the lcd display while the rest of the device is sleeping. the adc noise reduction mode stops the cpu and all i/o modules except asynchronous timer, lcd controller and adc, to minimize switching noise during adc conversions. in standby mode, the crystal/resonator oscillator is running while the rest of the device is sleeping. this allows very fast start-up combined with low-power consumption. the device is manufactured using atmel?s high density non-volatile memory technology. the on-chip isp flash allows the program memory to be reprogrammed in-system through an spi serial interface, by a conventional non-volatile memory programmer, or by an on-chip boot program running on the avr core. the boot program can use any interface to download the application program in the application flash memory. soft- ware in the boot flash section will continue to run while the application flash section is updated, providing true read-while-write operation. by combining an 8-bit risc cpu with in-system self-programmable flash on a monolithic chip, the atmel atmega169 is a powerful microcontroller that provides a highly flexible and cost effective solution to many embedded control applications. the atmega169 avr is supported with a full suite of program and system development tools including: c compilers, macro assemblers, program debugger/simulators, in-cir- cuit emulators, and evaluation kits. 5 atmega169v/l 2514j?avr?12/03 pin descriptions vcc digital supply voltage. gnd ground. port a (pa7..pa0) port a is an 8-bit bi-directional i/o port with internal pull-up resistors (selected for each bit). the port a output buffers have symmetrical drive characteristics with both high sink and source capability. as inputs, port a pins that are externally pulled low will source current if the pull-up resistors are activated. the port a pins are tri-stated when a reset condition becomes active, even if the clock is not running. port a also serves the functions of various special features of the atmega169 as listed on page 59. port b (pb7..pb0) port b is an 8-bit bi-directional i/o port with internal pull-up resistors (selected for each bit). the port b output buffers have symmetrical drive characteristics with both high sink and source capability. as inputs, port b pins that are externally pulled low will source current if the pull-up resistors are activated. the port b pins are tri-stated when a reset condition becomes active, even if the clock is not running. port b has better driving capabilities than the other ports. port b also serves the functions of various special features of the atmega169 as listed on page 60. port c (pc7..pc0) port c is an 8-bit bi-directional i/o port with internal pull-up resistors (selected for each bit). the port c output buffers have symmetrical drive characteristics with both high sink and source capability. as inputs, port c pins that are externally pulled low will source current if the pull-up resistors are activated. the port c pins are tri-stated when a reset condition becomes active, even if the clock is not running. port c also serves the functions of special features of the atmega169 as listed on page 63. port d (pd7..pd0) port d is an 8-bit bi-directional i/o port with internal pull-up resistors (selected for each bit). the port d output buffers have symmetrical drive characteristics with both high sink and source capability. as inputs, port d pins that are externally pulled low will source current if the pull-up resistors are activated. the port d pins are tri-stated when a reset condition becomes active, even if the clock is not running. port d also serves the functions of various special features of the atmega169 as listed on page 65. port e (pe7..pe0) port e is an 8-bit bi-directional i/o port with internal pull-up resistors (selected for each bit). the port e output buffers have symmetrical drive characteristics with both high sink and source capability. as inputs, port e pins that are externally pulled low will source current if the pull-up resistors are activated. the port e pins are tri-stated when a reset condition becomes active, even if the clock is not running. port e also serves the functions of various special features of the atmega169 as listed on page 67. port f (pf7..pf0) port f serves as the analog inputs to the a/d converter. port f also serves as an 8-bit bi-directional i/o port, if the a/d converter is not used. port pins can provide internal pull-up resistors (selected for each bit). the port f output 6 atmega169v/l 2514j?avr?12/03 buffers have symmetrical drive characteristics with both high sink and source capability. as inputs, port f pins that are externally pulled low will source current if the pull-up resistors are activated. the port f pins are tri-stated when a reset condition becomes active, even if the clock is not running. if the jtag interface is enabled, the pull-up resis- tors on pins pf7(tdi), pf5(tms), and pf4(tck) will be activated even if a reset occurs. port f also serves the functions of the jtag interface. port g (pg4..pg0) port g is a 5-bit bi-directional i/o port with internal pull-up resistors (selected for each bit). the port g output buffers have symmetrical drive characteristics with both high sink and source capability. as inputs, port g pins that are externally pulled low will source current if the pull-up resistors are activated. the port g pins are tri-stated when a reset condition becomes active, even if the clock is not running. port g also serves the functions of various special features of the atmega169 as listed on page 67. reset reset input. a low level on this pin for longer than the minimum pulse length will gener- ate a reset, even if the clock is not running. the minimum pulse length is given in table 16 on page 37. shorter pulses are not guaranteed to generate a reset. xtal1 input to the inverting oscillator amplifier and input to the internal clock operating circuit. xtal2 output from the inverting oscillator amplifier. avc c avcc is the supply voltage pin for port f and the a/d converter. it should be externally connected to v cc , even if the adc is not used. if the adc is used, it should be con- nected to v cc through a low-pass filter. aref this is the analog reference pin for the a/d converter. about code examples this documentation contains simple code examples that briefly show how to use various parts of the device. these code examples assume that the part specific header file is included before compilation. be aware that not all c compiler vendors include bit defini- tions in the header files and interrupt handling in c is compiler dependent. please confirm with the c compiler documentation for more details. 7 atmega169v/l 2514j?avr?12/03 avr cpu core introduction this section discusses the avr core architecture in general. the main function of the cpu core is to ensure correct program execution. the cpu must therefore be able to access memories, perform calculations, control peripherals, and handle interrupts. architectural overview figure 3. block diagram of the avr architecture in order to maximize performance and parallelism, the avr uses a harvard architecture ? with separate memories and buses for program and data. instructions in the program memory are executed with a single level pipelining. while one instruction is being exe- cuted, the next instruction is pre-fetched from the program memory. this concept enables instructions to be executed in every clock cycle. the program memory is in- system reprogrammable flash memory. the fast-access register file contains 32 x 8-bit general purpose working registers with a single clock cycle access time. this allows single-cycle arithmetic logic unit (alu) operation. in a typical alu operation, two operands are output from the register file, flash program memory instruction register instruction decoder program counter control lines 32 x 8 general purpose registrers alu status and control i/o lines eeprom data bus 8-bit data sram direct addressing indirect addressing interrupt unit spi unit watchdog timer analog comparator i/o module 2 i/o module1 i/o module n 8 atmega169v/l 2514j?avr?12/03 the operation is executed, and the result is stored back in the register file ? in one clock cycle. six of the 32 registers can be used as three 16-bit indirect address register pointers for data space addressing ? enabling efficient address calculations. one of the these address pointers can also be used as an address pointer for look up tables in flash pro- gram memory. these added function registers are the 16-bit x-, y-, and z-register, described later in this section. the alu supports arithmetic and logic operations between registers or between a con- stant and a register. single register operations can also be executed in the alu. after an arithmetic operation, the status register is updated to reflect information about the result of the operation. program flow is provided by conditional and unconditional jump and call instructions, able to directly address the whole address space. most avr instructions have a single 16-bit word format. every program memory address contains a 16- or 32-bit instruction. program flash memory space is divided in two sections, the boot program section and the application program section. both sections have dedicated lock bits for write and read/write protection. the spm instruction that writes into the application flash memory section must reside in the boot program section. during interrupts and subroutine calls, t he return address program counter (pc) is stored on the stack. the stack is effectively allocated in the general data sram, and consequently the stack size is only limited by the total sram size and the usage of the sram. all user programs must initialize the sp in the reset routine (before subroutines or interrupts are executed). the stack pointer (sp) is read/write accessible in the i/o space. the data sram can easily be accessed through the five different addressing modes supported in the avr architecture. the memory spaces in the avr architecture are all linear and regular memory maps. a flexible interrupt module has its control registers in the i/o space with an additional global interrupt enable bit in the status register. all interrupts have a separate interrupt vector in the interrupt vector table. the interrupts have priority in accordance with their interrupt vector position. the lower the interrupt vector address, the higher the priority. the i/o memory space contains 64 addresses for cpu peripheral functions as control registers, spi, and other i/o functions. the i/o memory can be accessed directly, or as the data space locations following those of the register file, 0x20 - 0x5f. in addition, the atmega169 has extended i/o space from 0x60 - 0xff in sram where only the st/sts/std and ld/lds/ldd instructions can be used. alu ? arithmetic logic unit the high-performance avr alu operates in direct connection with all the 32 general purpose working registers. within a single clock cycle, arithmetic operations between general purpose registers or between a register and an immediate are executed. the alu operations are divided into three main categories ? arithmetic, logical, and bit-func- tions. some implementations of the architecture also provide a powerful multiplier supporting both signed/unsigned multiplication and fractional format. see the ?instruc- tion set? section for a detailed description. 9 atmega169v/l 2514j?avr?12/03 status register the status register contains information about the result of the most recently executed arithmetic instruction. this information can be used for altering program flow in order to perform conditional operations. note that the status register is updated after all alu operations, as specified in the instruction set reference. this will in many cases remove the need for using the dedicated compare instructions, resulting in faster and more compact code. the status register is not automatically stored when entering an interrupt routine and restored when returning from an interrupt. this must be handled by software. the avr status register ? sreg ? is defined as: bit 7 ? i: global interrupt enable the global interrupt enable bit must be set for the interrupts to be enabled. the individ- ual interrupt enable control is then performed in separate control registers. if the global interrupt enable register is cleared, none of the interrupts are enabled independent of the individual interrupt enable settings. the i-bit is cleared by hardware after an interrupt has occurred, and is set by the reti instruction to enable subsequent interrupts. the i- bit can also be set and cleared by the application with the sei and cli instructions, as described in the instruction set reference. bit 6 ? t: bit copy storage the bit copy instructions bld (bit load) and bst (bit store) use the t-bit as source or destination for the operated bit. a bit from a register in the register file can be copied into t by the bst instruction, and a bit in t can be copied into a bit in a register in the register file by the bld instruction. bit 5 ? h: half carry flag the half carry flag h indicates a half carry in some arithmetic operations. half carry is useful in bcd arithmetic. see the ?instruction set description? for detailed information. bit 4 ? s: sign bit, s = n v the s-bit is always an exclusive or between the negative flag n and the two?s comple- ment overflow flag v. see the ?instruction set description? for detailed information. bit 3 ? v: two?s complement overflow flag the two?s complement overflow flag v supports two?s complement arithmetics. see the ?instruction set description? for detailed information. bit 2 ? n: negative flag the negative flag n indicates a negative result in an arithmetic or logic operation. see the ?instruction set description? for detailed information. bit 1 ? z: zero flag the zero flag z indicates a zero result in an arithmetic or logic operation. see the ?instruction set description? for detailed information. bit 76543210 i t h s v n z c sreg read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 10 atmega169v/l 2514j?avr?12/03 bit 0 ? c: carry flag the carry flag c indicates a carry in an arithmetic or logic operation. see the ?instruc- tion set description? for detailed information. general purpose register file the register file is optimized for the avr enhanced risc instruction set. in order to achieve the required performance and flexibility, the following input/output schemes are supported by the register file: one 8-bit output operand and one 8-bit result input two 8-bit output operands and one 8-bit result input two 8-bit output operands and one 16-bit result input one 16-bit output operand and one 16-bit result input figure 4 shows the structure of the 32 general purpose working registers in the cpu. figure 4. avr cpu general purpose working registers most of the instructions operating on the register file have direct access to all registers, and most of them are single cycle instructions. as shown in figure 4, each register is also assigned a data memory address, mapping them directly into the first 32 locations of the user data space. although not being phys- ically implemented as sram locations, this memory organization provides great flexibility in access of the registers, as the x-, y- and z-pointer registers can be set to index any register in the file. 70addr. r0 0x00 r1 0x01 r2 0x02 ? r13 0x0d general r14 0x0e purpose r15 0x0f working r16 0x10 registers r17 0x11 ? r26 0x1a x-register low byte r27 0x1b x-register high byte r28 0x1c y-register low byte r29 0x1d y-register high byte r30 0x1e z-register low byte r31 0x1f z-register high byte 11 atmega169v/l 2514j?avr?12/03 the x-register, y-register, and z-register the registers r26..r31 have some added functions to their general purpose usage. these registers are 16-bit address pointers for indirect addressing of the data space. the three indirect address registers x, y, and z are defined as described in figure 5. figure 5. the x-, y-, and z-registers in the different addressing modes these address registers have functions as fixed dis- placement, automatic increment, and automatic decrement (see the instruction set reference for details). stack pointer the stack is mainly used for storing temporary data, for storing local variables and for storing return addresses after interrupts and subroutine calls. the stack pointer regis- ter always points to the top of the stack. note that the stack is implemented as growing from higher memory locations to lower memory locations. this implies that a stack push command decreases the stack pointer. the stack pointer points to the data sram stack area where the subroutine and inter- rupt stacks are located. this stack space in the data sram must be defined by the program before any subroutine calls are ex ecuted or interrupts are enabled. the stack pointer must be set to point above 0x60. the stack pointer is decremented by one when data is pushed onto the stack with the push instruction, and it is decremented by two when the return address is pushed onto the stack with subroutine call or interrupt. the stack pointer is incremented by one when data is popped from the stack with the pop instruction, and it is incremented by two when data is popped from the stack with return from subroutine ret or return from interrupt reti. the avr stack pointer is implemented as two 8-bit registers in the i/o space. the num- ber of bits actually used is implementation dependent. note that the data space in some implementations of the avr architecture is so small that only spl is needed. in this case, the sph register will not be present. 15 xh xl 0 x-register 7 0 7 0 r27 (0x1b) r26 (0x1a) 15 yh yl 0 y-register 7 0 7 0 r29 (0x1d) r28 (0x1c) 15 zh zl 0 z-register 7 0 7 0 r31 (0x1f) r30 (0x1e) bit 151413121110 9 8 sp15 sp14 sp13 sp12 sp11 sp10 sp9 sp8 sph sp7 sp6 sp5 sp4 sp3 sp2 sp1 sp0 spl 76543210 read/write r/w r/w r/w r/w r/w r/w r/w r/w r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 00000000 12 atmega169v/l 2514j?avr?12/03 instruction execution timing this section describes the general access timing concepts for instruction execution. the avr cpu is driven by the cpu clock clk cpu , directly generated from the selected clock source for the chip. no internal clock division is used. figure 6 shows the parallel instruction fetches and instruction executions enabled by the harvard architecture and the fast-access register file concept. this is the basic pipelin- ing concept to obtain up to 1 mips per mhz with the corresponding unique results for functions per cost, functions per clocks, and functions per power-unit. figure 6. the parallel instruction fetches and instruction executions figure 7 shows the internal timing concept for the register file. in a single clock cycle an alu operation using two register operands is executed, and the result is stored back to the destination register. figure 7. single cycle alu operation reset and interrupt handling the avr provides several different interrupt sources. these interrupts and the separate reset vector each have a separate program vector in the program memory space. all interrupts are assigned individual enable bits which must be written logic one together with the global interrupt enable bit in the status register in order to enable the interrupt. depending on the program counter value, interrupts may be automatically disabled when boot lock bits blb02 or blb12 are programmed. this feature improves software security. see the section ?memory programming? on page 266 for details. the lowest addresses in the program memory space are by default defined as the reset and interrupt vectors. the complete list of vectors is shown in ?interrupts? on page 46. the list also determines the priority levels of the different interrupts. the lower the address the higher is the priority level. reset has the highest priority, and next is int0 ? the external interrupt request 0. the interrupt vectors can be moved to the start of the boot flash section by setting the ivsel bit in the mcu control register (mcucr). refer to ?interrupts? on page 46 for more information. the reset vector can also be clk 1st instruction fetch 1st instruction execute 2nd instruction fetch 2nd instruction execute 3rd instruction fetch 3rd instruction execute 4th instruction fetch t1 t2 t3 t4 cpu total execution time register operands fetch alu operation execute result write back t1 t2 t3 t4 clk cpu 13 atmega169v/l 2514j?avr?12/03 moved to the start of the boot flash section by programming the bootrst fuse, see ?boot loader support ? read-while-write self-programming? on page 252. when an interrupt occurs, the global interrupt enable i-bit is cleared and all interrupts are disabled. the user software can write logic one to the i-bit to enable nested inter- rupts. all enabled interrupts can then interrupt the current interrupt routine. the i-bit is automatically set when a return from interrupt instruction ? reti ? is executed. there are basically two types of interrupts. the first type is triggered by an event that sets the interrupt flag. for these interrupts, the program counter is vectored to the actual interrupt vector in order to exec ute the interrupt handling routine, and hardware clears the corresponding interrupt flag. interrupt flags can also be cleared by writing a logic one to the flag bit position(s) to be cleared. if an interrupt condition occurs while the corresponding interrupt enable bit is cleared, the interrupt flag will be set and remem- bered until the interrupt is enabled, or the flag is cleared by software. similarly, if one or more interrupt conditions occur while the global interrupt enable bit is cleared, the cor- responding interrupt flag(s) will be set and remembered until the global interrupt enable bit is set, and will then be executed by order of priority. the second type of interrupts will trigger as long as the interrupt condition is present. these interrupts do not necessarily have interrupt flags. if the interrupt condition disap- pears before the interrupt is enabled, the interrupt will not be triggered. when the avr exits from an interrupt, it will always return to the main program and exe- cute one more instruction before any pending interrupt is served. note that the status register is not automatically stored when entering an interrupt rou- tine, nor restored when returning from an interrupt routine. this must be handled by software. when using the cli instruction to disable interrupts, the interrupts will be immediately disabled. no interrupt will be executed after the cli instruction, even if it occurs simulta- neously with the cli instruction. the following example shows how this can be used to avoid interrupts during the timed eeprom write sequence. assembly code example in r16, sreg ; store sreg value cli ; disable interrupts during timed sequence sbi eecr, eemwe ; start eeprom write sbi eecr, eewe out sreg, r16 ; restore sreg value (i-bit) c code example char csreg; csreg = sreg; /* store sreg value */ /* disable interrupts during timed sequence */ _cli(); eecr |= (1< 15 atmega169v/l 2514j?avr?12/03 avr atmega169 memories this section describes the different memories in the atmega169. the avr architecture has two main memory spaces, the data memory and the program memory space. in addition, the atmega169 features an eeprom memory for data storage. all three memory spaces are linear and regular. in-system reprogrammable flash program memory the atmega169 contains 16k bytes on-chip in-system reprogrammable flash mem- ory for program storage. since all avr instru ctions are 16 or 32 bits wide, the flash is organized as 8k x 16. for software security, the flash program memory space is divided into two sections, boot program section and application program section. the flash memory has an endurance of at least 10,000 write/erase cycles. the atmega169 program counter (pc) is 13 bits wide, thus addressing the 8k program memory locations. the operation of boot program section and associated boot lock bits for software protection are described in detail in ?boot loader support ? read- while-write self-programming? on page 252. ?memory programming? on page 266 con- tains a detailed description on flash data serial downloading using the spi pins or the jtag interface. constant tables can be allocated within the entire program memory address space (see the lpm ? load program memory instruction description). timing diagrams for instruction fetch and execution are presented in ?instruction execu- tion timing? on page 12. figure 8. program memory map 0x0000 0x1fff program memory application flash section boot flash section 16 atmega169v/l 2514j?avr?12/03 sram data memory figure 9 shows how the atmega169 sram memory is organized. the atmega169 is a complex microcontroller with more peripheral units than can be supported within the 64 locations reserved in the opcode for the in and out instruc- tions. for the extended i/o space from 0x60 - 0xff in sram, only the st/sts/std and ld/lds/ldd instructions can be used. the lower 1,280 data memory locations address both the register file, the i/o memory, extended i/o memory, and the internal data sram. the first 32 locations address the register file, the next 64 location the standard i/o memory, then 160 locations of extended i/o memory, and the next 1024 locations address the internal data sram. the five different addressing modes for the data memory cover: direct, indirect with dis- placement, indirect, indirect with pre-decrement, and indirect with post-increment. in the register file, registers r26 to r31 feature the indirect addressing pointer registers. the direct addressing reaches the entire data space. the indirect with displacement mode reaches 63 address locations from the base address given by the y- or z-register. when using register indirect addressing modes with automatic pre-decrement and post- increment, the address registers x, y, and z are decremented or incremented. the 32 general purpose working registers, 64 i/o registers, 160 extended i/o regis- ters, and the 1,024 bytes of internal data sram in the atmega169 are all accessible through all these addressing modes. the register file is described in ?general purpose register file? on page 10. figure 9. data memory map 32 registers 64 i/o registers internal sram (1024 x 8) 0x0000 - 0x001f 0x0020 - 0x005f 0x04ff 0x0060 - 0x00ff data memory 160 ext i/o reg. 0x0100 17 atmega169v/l 2514j?avr?12/03 data memory access times this section describes the general access timing concepts for internal memory access. the internal data sram access is performed in two clk cpu cycles as described in figure 10. figure 10. on-chip data sram access cycles eeprom data memory the atmega169 contains 512 bytes of data eeprom memory. it is organized as a sep- arate data space, in which single bytes can be read and written. the eeprom has an endurance of at least 100,000 write/erase cycles. the access between the eeprom and the cpu is described in the following, specifying the eeprom address registers, the eeprom data register, and the eeprom control register. for a detailed description of spi, jtag and parallel data downloading to the eeprom, see page 281, page 285, and page 270 respectively. eeprom read/write access the eeprom access registers are accessible in the i/o space. the write access time for the eeprom is given in table 1. a self-timing function, how- ever, lets the user software detect when the next byte can be written. if the user code contains instructions that write the eeprom, some precautions must be taken. in heavily filtered power supplies, v cc is likely to rise or fall slowly on power-up/down. this causes the device for some period of time to run at a voltage lower than specified as minimum for the clock frequency used. see ?preventing eeprom corruption? on page 21. for details on how to avoid problems in these situations. in order to prevent unintentional eeprom writes, a specific write procedure must be fol- lowed. refer to the description of the eeprom control register for details on this. when the eeprom is read, the cpu is hal ted for four clock cycles before the next instruction is executed. when the eeprom is written, the cpu is halted for two clock cycles before the next instruction is executed. clk wr rd data data address address valid t1 t2 t3 compute address read write cpu memory access instruction next instruction 18 atmega169v/l 2514j?avr?12/03 the eeprom address register ? eearh and eearl bits 15..9 ? res: reserved bits these bits are reserved bits in the atmega169 and will always read as zero. bits 8..0 ? eear8..0: eeprom address the eeprom address registers ? eearh and eearl specify the eeprom address in the 512 bytes eeprom space. the eeprom data bytes are addressed linearly between 0 and 511. the initial value of eear is undefined. a proper value must be writ- ten before the eeprom may be accessed. the eeprom data register ? eedr bits 7..0 ? eedr7..0: eeprom data for the eeprom write operation, the eedr register contains the data to be written to the eeprom in the address given by the eear register. for the eeprom read oper- ation, the eedr contains the data read out from the eeprom at the address given by eear. the eeprom control register ? eecr bits 7..4 ? res: reserved bits these bits are reserved bits in the atmega169 and will always read as zero. bit 3 ? eerie: eeprom ready interrupt enable writing eerie to one enables the eeprom ready interrupt if the i bit in sreg is set. writing eerie to zero disables the interrupt. the eeprom ready interrupt generates a constant interrupt when eewe is cleared. bit 2 ? eemwe: eeprom master write enable the eemwe bit determines whether setting eewe to one causes the eeprom to be written. when eemwe is set, setting eewe within four clock cycles will write data to the eeprom at the selected address if eemwe is zero, setting eewe will have no effect. when eemwe has been written to one by software, hardware clears the bit to zero after four clock cycles. see the description of the eewe bit for an eeprom write procedure. bit 151413121110 9 8 ???????eear8eearh eear7 eear6 eear5 eear4 eear3 eear2 eear1 eear0 eearl 76543210 read/write r r r r r r r r/w r/w r/w r/w r/w r/w r/w r/w r/w initial value0000000x xxxxxxxx bit 76543210 msb lsb eedr read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 ? ? ? ? eerie eemwe eewe eere eecr read/write r r r r r/w r/w r/w r/w initial value 0 0 0 0 0 0 x 0 19 atmega169v/l 2514j?avr?12/03 bit 1 ? eewe: eeprom write enable the eeprom write enable signal eewe is the write strobe to the eeprom. when address and data are correctly set up, the eewe bit must be written to one to write the value into the eeprom. the eemwe bit must be written to one before a logical one is written to eewe, otherwise no eeprom write takes place. the following procedure should be followed when writing the eeprom (the order of steps 3 and 4 is not essential): 1. wait until eewe becomes zero. 2. wait until spmen in spmcsr becomes zero. 3. write new eeprom address to eear (optional). 4. write new eeprom data to eedr (optional). 5. write a logical one to the eemwe bit while writing a zero to eewe in eecr. 6. within four clock cycles after setting eemwe, write a logical one to eewe. the eeprom can not be programmed during a cpu write to the flash memory. the software must check that the flash programming is completed before initiating a new eeprom write. step 2 is only relevant if the software contains a boot loader allowing the cpu to program the flash. if the flash is never being updated by the cpu, step 2 can be omitted. see ?boot loader support ? read-while-write self-programming? on page 252 for details about boot programming. caution: an interrupt between step 5 and step 6 will make the write cycle fail, since the eeprom master write enable will time-out. if an interrupt routine accessing the eeprom is interrupting another eeprom access, the eear or eedr register will be modified, causing the interrupted eeprom access to fail. it is recommended to have the global interrupt flag cleared during all the steps to avoid these problems. when the write access time has elapsed, the eewe bit is cleared by hardware. the user software can poll this bit and wait for a zero before writing the next byte. when eewe has been set, the cpu is halted for two cycles before the next instruction is executed. bit 0 ? eere: eeprom read enable the eeprom read enable signal eere is the read strobe to the eeprom. when the correct address is set up in the eear register, the eere bit must be written to a logic one to trigger the eeprom read. the eeprom read access takes one instruction, and the requested data is available immediately. when the eeprom is read, the cpu is halted for four cycles before the next instruction is executed. the user should poll the eewe bit before starting the read operation. if a write operation is in progress, it is neither possible to read the eeprom, nor to change the eear register. the calibrated oscillator is used to time the eeprom accesses. table 1 lists the typical programming time for eeprom access from the cpu. table 1. eeprom programming time symbol number of calibrated rc oscillator cycles typ programming time eeprom write (from cpu) 67 584 8.5 ms 20 atmega169v/l 2514j?avr?12/03 the following code examples show one assembly and one c function for writing to the eeprom. the examples assume that interrupts are controlled (e.g. by disabling inter- rupts globally) so that no interrupts will occur during execution of these functions. the examples also assume that no flash boot loader is present in the software. if such code is present, the eeprom write function must also wait for any ongoing spm com- mand to finish. assembly code example eeprom_write: ; wait for completion of previous write sbic eecr,eewe rjmp eeprom_write ; set up address (r18:r17) in address register out eearh, r18 out eearl, r17 ; write data (r16) to data register out eedr,r16 ; write logical one to eemwe sbi eecr,eemwe ; start eeprom write by setting eewe sbi eecr,eewe ret c code example void eeprom_write( unsigned int uiaddress, unsigned char ucdata) { /* wait for completion of previous write */ while(eecr & (1< 23 atmega169v/l 2514j?avr?12/03 system clock and clock options clock systems and their distribution figure 11 presents the principal clock systems in the avr and their distribution. all of the clocks need not be active at a given time. in order to reduce power consumption, the clocks to modules not being used can be halted by using different sleep modes, as described in ?power management and sleep modes? on page 32. the clock systems are detailed below. figure 11. clock distribution cpu clock ? clk cpu the cpu clock is routed to parts of the system concerned with operation of the avr core. examples of such modules are the general purpose register file, the status reg- ister and the data memory holding the stack pointer. halting the cpu clock inhibits the core from performing general operations and calculations. i/o clock ? clk i/o the i/o clock is used by the majority of the i/o modules, like timer/counters, spi, and usart. the i/o clock is also used by the external interrupt module, but note that some external interrupts are detected by asynchronous logic, allowing such interrupts to be detected even if the i/o clock is halted. also note that start condition detection in the usi module is carried out asynchronously when clk i/o is halted, enabling usi start condition detection in all sleep modes. flash clock ? clk flash the flash clock controls operation of the flash interface. the flash clock is usually active simultaneously with the cpu clock. asynchronous timer clock ? clk asy the asynchronous timer clock allows the asynchronous timer/counter and the lcd controller to be clocked directly from an external clock or an external 32 khz clock crys- tal. the dedicated clock domain allows using this timer/counter as a real-time counter even when the device is in sleep mode. it also allows the lcd controller output to con- tinue while the rest of the device is in sleep mode. general i/o modules asynchronous timer/counter cpu core ram clk i/o clk asy avr clock control unit clk cpu flash and eeprom clk flash source clock watchdog timer watchdog oscillator reset logic clock multiplexer watchdog clock calibrated rc oscillator timer/counter oscillator crystal oscillator low-frequency crystal oscillator external clock lcd controller system clock prescaler 24 atmega169v/l 2514j?avr?12/03 adc clock ? clk adc the adc is provided with a dedicated clock domain. this allows halting the cpu and i/o clocks in order to reduce noise generated by digital circuitry. this gives more accu- rate adc conversion results. clock sources the device has the following clock source options, selectable by flash fuse bits as shown below. the clock from the selected source is input to the avr clock generator, and routed to the appropriate modules. note: 1. for all fuses ?1? means unprogrammed while ?0? means programmed. the various choices for each clocking option is given in the following sections. when the cpu wakes up from power-down or power-save, the selected clock source is used to time the start-up, ensuring stable oscillator operation before instruction execution starts. when the cpu starts from reset, there is an additional delay allowing the power to reach a stable level before commencing normal operation. the watchdog oscillator is used for timing this real-time part of the star t-up time. the number of wdt oscillator cycles used for each time-out is shown in table 3. the frequency of the watchdog oscillator is voltage dependent as shown in ?atmega169 typical characteristics ? preliminary data? on page 304. default clock source the device is shipped with cksel = ?0010?, sut = ?10?, and ckdiv8 programmed. the default clock source setting is the inter nal rc oscillator with longest start-up time and an initial system clock prescaling of 8. this default setting ensures that all users can make their desired clock source setting using an in-system or parallel programmer. table 2. device clocking options select (1) device clocking option cksel3..0 external crystal/ceramic resonator 1111 - 1000 external low-frequency crystal 0111 - 0100 calibrated internal rc oscillator 0010 external clock 0000 reserved 0011, 0001 table 3. number of watchdog oscillator cycles typ time-out (v cc = 5.0v) typ time-out (v cc = 3.0v) number of cycles 4.1 ms 4.3 ms 4k (4,096) 65 ms 69 ms 64k (65,536) 25 atmega169v/l 2514j?avr?12/03 crystal oscillator xtal1 and xtal2 are input and output, respectively, of an inverting amplifier which can be configured for use as an on-chip oscillator, as shown in figure 12. either a quartz crystal or a ceramic resonator may be used. c1 and c2 should always be equal for both crystals and resonators. the optimal value of the capacitors depends on the crystal or resonator in use, the amount of stray capac- itance, and the electromagnetic noise of the environment. some initial guidelines for choosing capacitors for use with crystals are given in table 4. for ceramic resonators, the capacitor values given by the manufacturer should be used. figure 12. crystal oscillator connections the oscillator can operate in three different modes, each optimized for a specific fre- quency range. the operating mode is selected by the fuses cksel3..1 as shown in table 4. notes: 1. this option should not be used with crystals, only with ceramic resonators. the cksel0 fuse together with the sut1..0 fuses select the start-up times as shown in table 5. table 4. crystal oscillator operating modes cksel3..1 frequency range (mhz) recommended range for capacitors c1 and c2 for use with crystals (pf) 100 (1) 0.4 - 0.9 ? 101 0.9 - 3.0 12 - 22 110 3.0 - 8.0 12 - 22 111 8.0 - 12 - 22 xtal2 xtal1 gnd c2 c1 26 atmega169v/l 2514j?avr?12/03 notes: 1. these options should only be used when not operating close to the maximum fre- quency of the device, and only if frequency stability at start-up is not important for the application. these options are not suitable for crystals. 2. these options are intended for use wi th ceramic resonators and will ensure fre- quency stability at start-up. they can also be used with crystals when not operating close to the maximum frequency of the device, and if frequency stability at start-up is not important for the application. low-frequency crystal oscillator to use a 32.768 khz watch crystal as the clock source for the device, the low-frequency crystal oscillator must be selected by se tting the cksel fuses to ?0100?, ?0101?, ?0110?, or ?0111?. the crystal should be connected as shown in figure 12. when this oscillator is selected, start-up times are determined by the sut fuses as shown in table 6 and cksel1..0 as shown in table 7. table 5. start-up times for the crystal oscillator clock selection cksel0 sut1..0 start-up time from power-down and power-save additional delay from reset (v cc = 5.0v) recommended usage 0 00 258 ck (1) 14ck + 4.1 ms ceramic resonator, fast rising power 0 01 258 ck (1) 14ck + 65 ms ceramic resonator, slowly rising power 010 1k ck (2) 14ck ceramic resonator, bod enabled 011 1k ck (2) 14ck + 4.1 ms ceramic resonator, fast rising power 100 1k ck (2) 14ck + 65 ms ceramic resonator, slowly rising power 1 01 16k ck 14ck crystal oscillator, bod enabled 1 10 16k ck 14ck + 4.1 ms crystal oscillator, fast rising power 1 11 16k ck 14ck + 65 ms crystal oscillator, slowly rising power table 6. start-up times for the low-frequency crystal oscillator clock selection sut1..0 additional delay from reset (v cc = 5.0v) recommended usage 00 14ck fast rising power or bod enabled 01 14ck + 4.1 ms slowly rising power 10 14ck + 65 ms stable frequency at start-up 11 reserved 27 atmega169v/l 2514j?avr?12/03 note: 1. these options should only be used if frequency stability at start-up is not important for the application calibrated internal rc oscillator the calibrated internal rc oscillator provides a fixed 8.0 mhz clock. the frequency is nominal value at 3v and 25 c. if 8 mhz frequency exceeds the specification of the device (depends on v cc ), the ckdiv8 fuse must be programmed in order to divide the internal frequency by 8 during start-up. the device is shipped with the ckdiv8 fuse programmed. see ?system clock prescaler? on page 30. for more details. this clock may be selected as the system clock by programming the cksel fuses as shown in table 8. if selected, it will operate with no external components. during reset, hardware loads the calibration byte into the osccal register and thereby automatically cali- brates the rc oscillator. at 3v and 25 c, this calibration gives a frequency within 10% of the nominal frequency. using run-time calibration methods as described in application notes available at www.atmel.com/avr it is possible to achieve 2% accuracy at any given v cc and temperature. when this oscillator is used as the chip clock, the watch- dog oscillator will still be used for the watchdog timer and for the reset time-out. for more information on the pre-programmed calibration value, see the section ?calibration byte? on page 270. note: 1. the device is shipped with this option selected. when this oscillator is selected, start-up times are determined by the sut fuses as shown in table 9. selecting internal rc oscillator allows the xtal1/tosc1 and xtal2/tosc2 pins to be used as timer oscillator pins. note: 1. the device is shipped with this option selected. table 7. start-up times for the low-frequency crystal oscillator clock selection cksel3..0 start-up time from power-down and power-save recommended usage 0100 (1) 1k ck 0101 32k ck stable frequency at start-up 0110 (1) 1k ck 0111 32k ck stable frequency at start-up table 8. internal calibrated rc oscillator operating modes (1) cksel3..0 nominal frequency 0010 8.0 mhz table 9. start-up times for the internal calibrated rc oscillator clock selection sut1..0 start-up time from power- down and power-save additional delay from reset (v cc = 5.0v) recommended usage 00 6 ck 14ck bod enabled 01 6 ck 14ck + 4.1 ms fast rising power 10 (1) 6 ck 14ck + 65 ms slowly rising power 11 reserved 28 atmega169v/l 2514j?avr?12/03 oscillator calibration register ? osccal bits 6..0 ? cal6..0: oscillator calibration value writing the calibration byte to this address will trim the internal oscillator to remove pro- cess variations from the oscillator frequency. this is done automatically during chip reset. when osccal is zero, the lowest available frequency is chosen. writing non- zero values to this register will increase the frequency of the internal oscillator. writing 0x7f to the register gives the highest available frequency. the calibrated oscillator is used to time eeprom and flash access. if eeprom or flash is written, do not cali- brate to more than 10% above the nominal frequency. otherwise, the eeprom or flash write may fail. note that the oscillator is intended for calibration to 8.0 mhz. tuning to other values is not guaranteed, as indicated in table 10. bit 76543210 ? cal6 cal5 cal4 cal3 cal2 cal1 cal0 osccal read/write r r/w r/w r/w r/w r/w r/w r/w initial value device specific calibration value table 10. internal rc oscillator frequency range. osccal value min frequency in percentage of nominal frequency max frequency in percentage of nominal frequency 0x00 50% 100% 0x3f 75% 150% 0x7f 100% 200% 29 atmega169v/l 2514j?avr?12/03 external clock to drive the device from an external clock source, xtal1 should be driven as shown in figure 13. to run the device on an external clock, the cksel fuses must be pro- grammed to ?0000?. figure 13. external clock drive configuration when this clock source is selected, start-up times are determined by the sut fuses as shown in table 12. when applying an external clock, it is required to avoid sudden changes in the applied clock frequency to ensure stable operation of the mcu. a variation in frequency of more than 2% from one clock cycle to the next can lead to unpredictable behavior. it is required to ensure that the mcu is kept in reset during such changes in the clock frequency. note that the system clock prescaler can be used to implement run-time changes of the internal clock frequency while still ensuring stable operation. refer to ?system clock prescaler? on page 30 for details. clock output buffer when the ckout fuse is programmed, the system clock will be output on clko. this mode is suitable when chip clock is used to drive other circuits on the system. the clock will be output also during reset and the normal operation of i/o pin will be overridden when the fuse is programmed. any clock source, including internal rc oscillator, can be selected when clko serves as clock output. if the system clock prescaler is used, it is the divided system clock that is output when the ckout fuse is programmed. table 11. crystal oscillator clock frequency cksel3..0 frequency range 0000 0 - 16 mhz table 12. start-up times for the external clock selection sut1..0 start-up time from power- down and power-save additional delay from reset (v cc = 5.0v) recommended usage 00 6 ck 14ck bod enabled 01 6 ck 14ck + 4.1 ms fast rising power 10 6 ck 14ck + 65 ms slowly rising power 11 reserved nc external clock signal xtal2 xtal1 gnd 30 atmega169v/l 2514j?avr?12/03 timer/counter oscillator atmega169 share the timer/counter osc illator pins (tosc1 and tosc2) with xtal1 and xtal2. this means that the timer/counter oscillator can only be used when the calibrated internal rc oscillator is selected as system clock source. the oscillator is optimized for use with a 32.768 khz watch crystal. see figure 12 on page 25 for crystal connection. applying an external clock source to tosc1 can be done if extclk in the assr reg- ister is written to logic one. see ?asynchronous operation of the timer/counter? on page 138 for further description on selecting external clock as input instead of a 32 khz crystal. system clock prescaler the atmega169 system clock can be divided by setting the clock prescale register ? clkpr. this feature can be used to decrease power consumption when the require- ment for processing power is low. this can be used with all clock source options, and it will affect the clock frequency of the cpu and all synchronous peripherals. clk i/o , clk adc , clk cpu , and clk flash are divided by a factor as shown in table 13. clock prescale register ? clkpr bit 7 ? clkpce: clock prescaler change enable the clkpce bit must be written to logic one to enable change of the clkps bits. the clkpce bit is only updated when the other bits in clkpr are simultaneously written to zero. clkpce is cleared by hardware four cycles after it is written or when clkps bits are written. rewriting the clkpce bit within this time-out period does neither extend the time-out period, nor clear the clkpce bit. bits 3..0 ? clkps3..0: clock prescaler select bits 3 - 0 these bits define the division factor between the selected clock source and the internal system clock. these bits can be written run-time to vary the clock frequency to suit the application requirements. as the divider divides the master clock input to the mcu, the speed of all synchronous peripherals is reduced when a division factor is used. the divi- sion factors are given in table 13. to avoid unintentional changes of clock frequency, a special write procedure must be followed to change the clkps bits: 1. write the clock prescaler change enable (clkpce) bit to one and all other bits in clkpr to zero. 2. within four cycles, write the desired value to clkps while writing a zero to clkpce. interrupts must be disabled when changing prescaler setting to make sure the write pro- cedure is not interrupted. the ckdiv8 fuse determines the initial value of the clkps bits. if ckdiv8 is unpro- grammed, the clkps bits will be reset to ?0000?. if ckdiv8 is programmed, clkps bits are reset to ?0011?, giving a division factor of 8 at start up. this feature should be used if the selected clock source has a higher frequency than the maximum frequency of the device at the present operating conditions. note that any value can be written to the clkps bits regardless of the ckdiv8 fuse setting. the application software must ensure that a sufficient division factor is chosen if the selected clock source has a higher bit 76543210 clkpce ? ? ? clkps3 clkps2 clkps1 clkps0 clkpr read/write r/w r r r r/w r/w r/w r/w initial value 0 0 0 0 see bit description 31 atmega169v/l 2514j?avr?12/03 frequency than the maximum frequency of the device at the present operating condi- tions. the device is shipped with the ckdiv8 fuse programmed. switching time when switching between prescaler settings, the system clock prescaler ensures that no glitches occur in the clock system and that no intermediate frequency is higher than neither the clock frequency corresponding to the previous setting, nor the clock fre- quency corresponding to the new setting. the ripple counter that implements the prescaler runs at the frequency of the undivided clock, which may be faster than the cpu?s clock frequency. hence, it is not possible to determine the state of the prescaler ? even if it were readable, and the exact time it takes to switch from one clock division to another cannot be exactly predicted. from the time the clkps values are written, it takes between t1 + t2 and t1 + 2*t2 before the new clock frequency is active. in this interval, 2 active clock edges are pro- duced. here, t1 is the previous clock period, and t2 is the period corresponding to the new prescaler setting. table 13. clock prescaler select clkps3 clkps2 clkps1 clkps0 clock division factor 0000 1 0001 2 0010 4 0011 8 0100 16 0101 32 0110 64 0111 128 1000 256 1 0 0 1 reserved 1 0 1 0 reserved 1 0 1 1 reserved 1 1 0 0 reserved 1 1 0 1 reserved 1 1 1 0 reserved 1 1 1 1 reserved 32 atmega169v/l 2514j?avr?12/03 power management and sleep modes sleep modes enable the application to shut down unused modules in the mcu, thereby saving power. the avr provides various sleep modes allowing the user to tailor the power consumption to the application?s requirements. to enter any of the five sleep modes, the se bit in smcr must be written to logic one and a sleep instruction must be executed. the sm2, sm1, and sm0 bits in the smcr register select which sleep mode (idle, adc noise reduction, power-down, power- save, or standby) will be activated by the sleep instruction. see table 14 for a sum- mary. if an enabled interrupt occurs while the mcu is in a sleep mode, the mcu wakes up. the mcu is then halted for four cycles in addition to the start-up time, executes the interrupt routine, and resumes execution from the instruction following sleep. the con- tents of the register file and sram are unaltered when the device wakes up from sleep. if a reset occurs during sleep mode, the mcu wakes up and executes from the reset vector. figure 11 on page 23 presents the different clock systems in the atmega169, and their distribution. the figure is helpful in selecting an appropriate sleep mode. sleep mode control register ? smcr the sleep mode control register contains control bits for power management. bits 3, 2, 1 ? sm2..0: sleep mode select bits 2, 1, and 0 these bits select between the five available sleep modes as shown in table 14. note: 1. standby mode is only recommended for use with external crystals or resonators. bit 1 ? se: sleep enable the se bit must be written to logic one to make the mcu enter the sleep mode when the sleep instruction is executed. to avoid the mcu entering the sleep mode unless it is the programmer?s purpose, it is recommended to write the sleep enable (se) bit to one just before the execution of the sleep instruction and to clear it immediately after wak- ing up. bit 76543210 ? ? ? ? sm2 sm1 sm0 se smcr read/write r r r r r/w r/w r/w r/w initial value00000000 table 14. sleep mode select sm2 sm1 sm0 sleep mode 000idle 0 0 1 adc noise reduction 010power-down 011power-save 100reserved 101reserved 1 1 0 standby (1) 111reserved 33 atmega169v/l 2514j?avr?12/03 idle mode when the sm2..0 bits are written to 000, the sleep instruction makes the mcu enter idle mode, stopping the cpu but allowing lcd controller, the spi, usart, analog comparator, adc, usi, timer/counters, watchdog, and the interrupt system to con- tinue operating. this sleep mode basically halts clk cpu and clk flash , while allowing the other clocks to run. idle mode enables the mcu to wake up from external triggered interrupts as well as internal ones like the timer overflow and usart transmit complete interrupts. if wake-up from the analog comparator interr upt is not required, the analog comparator can be powered down by setting the acd bit in the analog comparator control and sta- tus register ? acsr. this will reduce power consumption in idle mode. if the adc is enabled, a conversion starts automatically when this mode is entered. adc noise reduction mode when the sm2..0 bits are written to 001, the sleep instruction makes the mcu enter adc noise reduction mode, stopping the cpu but allowing the adc, the external inter- rupts, the usi start condition detection, timer/counter2, lcd controller, and the watchdog to continue operating (if enabled). this sleep mode basically halts clk i/o , clk cpu , and clk flash , while allowing the other clocks to run. this improves the noise environment for the adc, enabling higher resolution measure- ments. if the adc is enabled, a conversion starts automatically when this mode is entered. apart form the adc conversion complete interrupt, only an external reset, a watchdog reset, a brown-out reset, an lcd controller interrupt, usi start condition interrupt, a timer/counter2 interrupt, an spm/eeprom ready interrupt, an external level interrupt on int0 or a pin change interrupt can wake up the mcu from adc noise reduction mode. power-down mode when the sm2..0 bits are written to 010, the sleep instruction makes the mcu enter power-down mode. in this mode, the external oscillator is stopped, while the external interrupts, the usi start condition detection, and the watchdog continue operating (if enabled). only an external reset, a watchdog reset, a brown-out reset, usi start con- dition interrupt, an external level interrupt on int0, or a pin change interrupt can wake up the mcu. this sleep mode basically halts all generated clocks, allowing operation of asynchronous modules only. note that if a level triggered interrupt is used for wake-up from power-down mode, the changed level must be held for some time to wake up the mcu. refer to ?external inter- rupts? on page 76 for details. when waking up from power-down mode, there is a delay from the wake-up condition occurs until the wake-up becomes effective. this allows the clock to restart and become stable after having been stopped. the wake-up period is defined by the same cksel fuses that define the reset time-out period, as described in ?clock sources? on page 24. power-save mode when the sm2..0 bits are written to 011, the sleep instruction makes the mcu enter power-save mode. this mode is identical to power-down, with one exception: if timer/counter2 and/or the lcd controller are enabled, they will keep running during sleep. the device can wake up from either timer overflow or output compare event from timer/counter2 if the corresponding timer/counter2 interrupt enable bits are set in timsk2, and the global interrupt enable bit in sreg is set. it can also wake up from an lcd controller interrupt. if neither timer/counter2 nor the lcd controller is running, power-down mode is rec- ommended instead of power-save mode. 34 atmega169v/l 2514j?avr?12/03 the lcd controller and timer/counter2 can be clocked both synchronously and asyn- chronously in power-save mode. the clock source for the two modules can be selected independent of each other. if neither the lcd controller nor the timer/counter2 is using the asynchronous clock, the timer/counter oscillator is stopped during sleep. if neither the lcd controller nor the timer/counter2 is using the synchronous clock, the clock source is stopped during sleep. note that even if the synchronous clock is running in power-save, this clock is only available for the lcd controller and timer/counter2. standby mode when the sm2..0 bits are 110 and an external crystal/resonator clock option is selected, the sleep instruction makes the mcu enter standby mode. this mode is identical to power-down with the exception that the oscillator is kept running. from standby mode, the device wakes up in six clock cycles. notes: 1. only recommended with external crystal or resonator selected as clock source. 2. if either lcd controller or timer/counter2 is running in asynchronous mode. 3. for int0, only level interrupt. minimizing power consumption there are several issues to consider when trying to minimize the power consumption in an avr controlled system. in general, sleep modes should be used as much as possi- ble, and the sleep mode should be selected so that as few as possible of the device?s functions are operating. all functions not needed should be disabled. in particular, the following modules may need special consideration when trying to achieve the lowest possible power consumption. analog to digital converter if enabled, the adc will be enabled in all sleep modes. to save power, the adc should be disabled before entering any sleep mode. when the adc is turned off and on again, the next conversion will be an extended conversion. refer to ?analog to digital con- verter? on page 192 for details on adc operation. analog comparator when entering idle mode, the analog comparator should be disabled if not used. when entering adc noise reduction mode, the analog comparator should be disabled. in other sleep modes, the analog comparator is automatically disabled. however, if the analog comparator is set up to use the internal voltage reference as input, the analog comparator should be disabled in all sleep modes. otherwise, the internal voltage ref- erence will be enabled, independent of sleep mode. refer to ?analog comparator? on page 189 for details on how to configure the analog comparator. table 15. active clock domains and wake-up sources in the different sleep modes. active clock domains oscillators wake-up sources sleep mode clk cpu clk flash clk io clk adc clk asy main clock source enabled timer osc enabled int0 and pin chang e usi start condition lcd controller timer2 spm/ eeprom ready adc other i/o idle x x x x x (2) xx xxxxx adc noise reduction x x x x (2) x (3) xx (2) x (2) xx power-down x (3) x power-save x x x (3) xxx standby (1) xx (3) x 35 atmega169v/l 2514j?avr?12/03 brown-out detector if the brown-out detector is not needed by the application, this module should be turned off. if the brown-out detector is enabled by the bodlevel fuses, it will be enabled in all sleep modes, and hence, always consume power. in the deeper sleep modes, this will contribute significantly to the total current consumption. refer to ?brown-out detec- tion? on page 39 for details on how to configure the brown-out detector. internal voltage reference the internal voltage reference will be enabled when needed by the brown-out detec- tion, the analog comparator or the adc. if these modules are disabled as described in the sections above, the internal voltage reference will be disabled and it will not be con- suming power. when turned on again, the user must allow the reference to start up before the output is used. if the reference is kept on in sleep mode, the output can be used immediately. refer to ?internal voltage reference? on page 41 for details on the start-up time. watchdog timer if the watchdog timer is not needed in the application, the module should be turned off. if the watchdog timer is enabled, it will be enabled in all sleep modes, and hence, always consume power. in the deeper sleep modes, this will contribute significantly to the total current consumption. refer to ?watchdog timer? on page 42 for details on how to configure the watchdog timer. port pins when entering a sleep mode, all port pins should be configured to use minimum power. the most important is then to ensure that no pins drive resistive loads. in sleep modes where both the i/o clock (clk i/o ) and the adc clock (clk adc ) are stopped, the input buff- ers of the device will be disabled. this ensures that no power is consumed by the input logic when not needed. in some cases, the input logic is needed for detecting wake-up conditions, and it will then be enabled. refer to the section ?digital input enable and sleep modes? on page 55 for details on which pins are enabled. if the input buffer is enabled and the input signal is left floating or have an analog signal level close to v cc /2, the input buffer will use excessive power. for analog input pins, the digital input buffer should be disabled at all times. an analog signal level close to v cc /2 on an input pin can cause significant current even in active mode. digital input buffers can be disabled by writing to the digital input disable regis- ters (didr1 and didr0). refer to ?digital input disable register 1 ? didr1? on page 191 and ?digital input disable register 0 ? didr0? on page 209 for details. jtag interface and on-chip debug system if the on-chip debug system is enabled by the ocden fuse and the chip enter power down or power save sleep mode, the main clock source remains enabled. in these sleep modes, this will contribute significantly to the total current consumption. there are three alternative ways to avoid this: disable ocden fuse. disable jtagen fuse. write one to the jtd bit in mcucsr. the tdo pin is left floating when the jtag interface is enabled while the jtag tap controller is not shifting data. if the hardware connected to the tdo pin does not pull up the logic level, power consumption will increase. note that the tdi pin for the next device in the scan chain contains a pull-up that avoids this problem. writing the jtd bit in the mcucsr register to one or leaving the jtag fuse unprogrammed disables the jtag interface. 36 atmega169v/l 2514j?avr?12/03 system control and reset resetting the avr during reset, all i/o registers are set to their initial values, and the program starts exe- cution from the reset vector. the instruction placed at the reset vector must be a jmp ? absolute jump ? instruction to the reset handling routine. if the program never enables an interrupt source, the interrupt vectors are not used, and regular program code can be placed at these locations. this is also the case if the reset vector is in the application section while the interrupt vectors are in the boot section or vice versa. the circuit diagram in figure 14 shows the reset logic. table 16 defines the electrical param- eters of the reset circuitry. the i/o ports of the avr are immediately reset to their initial state when a reset source goes active. this does not require any clock source to be running. after all reset sources have gone inactive, a delay counter is invoked, stretching the internal reset. this allows the power to reach a stable level before normal operation starts. the time-out period of the delay c ounter is defined by the user through the sut and cksel fuses. the different selections for the delay period are presented in ?clock sources? on page 24. reset sources the atmega169 has five sources of reset: power-on reset. the mcu is reset when the supply voltage is below the power-on reset threshold (v pot ). external reset. the mcu is reset when a low level is present on the reset pin for longer than the minimum pulse length. watchdog reset. the mcu is reset when the watchdog timer period expires and the watchdog is enabled. brown-out reset. the mcu is reset when the supply voltage v cc is below the brown-out reset threshold (v bot ) and the brown-out detector is enabled. jtag avr reset. the mcu is reset as long as there is a logic one in the reset register, one of the scan chains of the jtag system. refer to the section ?ieee 1149.1 (jtag) boundary-scan? on page 232 for details. 37 atmega169v/l 2514j?avr?12/03 figure 14. reset logic notes: 1. the power-on reset will not work unless the supply voltage has been below v pot (falling) table 16. reset characteristics symbol parameter condition min typ max units v pot power-on reset threshold voltage (rising) t a = -40c to 85c 0.7 1.0 1.4 v power-on reset threshold voltage (falling) (1) t a = -40c to 85c 0.6 0.9 1.3 v v rst reset pin threshold voltage v cc = 3v 0.1 v cc 0.9 v cc v t rst minimum pulse width on reset pin v cc = 3v 2.5 s mcu status register (mcusr) brown-out reset circuit bodlevel [2..0] delay counters cksel[3:0] ck timeout wdrf borf extrf porf data b u s clock generator spike filter pull-up resistor jtrf jtag reset register watchdog oscillator sut[1:0] power-on reset circuit 38 atmega169v/l 2514j?avr?12/03 power-on reset a power-on reset (por) pulse is generated by an on-chip detection circuit. the detec- tion level is defined in table 16. the por is activated whenever v cc is below the detection level. the por circuit can be used to trigger the start-up reset, as well as to detect a failure in supply voltage. a power-on reset (por) circuit ensures that the device is reset from power-on. reach- ing the power-on reset threshold voltage invokes the delay counter, which determines how long the device is kept in reset after v cc rise. the reset signal is activated again, without any delay, when v cc decreases below the detection level. figure 15. mcu start-up, reset tied to v cc figure 16. mcu start-up, reset extended externally v reset time-out internal reset t tout v pot v rst cc reset time-out internal reset t tout v pot v rst v cc 39 atmega169v/l 2514j?avr?12/03 external reset an external reset is generated by a low level on the reset pin. reset pulses longer than the minimum pulse width (see table 16) will generate a reset, even if the clock is not running. shorter pulses are not guaran teed to generate a reset. when the applied signal reaches the reset threshold voltage ? v rst ? on its positive edge, the delay counter starts the mcu after the time-out period ? t tout ? has expired. figure 17. external reset during operation brown-out detection atmega169 has an on-chip brown-out detection (bod) circuit for monitoring the v cc level during operation by comparing it to a fixed trigger level. the trigger level for the bod can be selected by the bodlevel fuses. the trigger level has a hysteresis to ensure spike free brown-out detection. the hysteresis on the detection level should be interpreted as v bot+ = v bot + v hyst /2 and v bot- = v bot - v hyst /2. note: 1. v bot may be below nominal minimum operating voltage for some devices. for devices where this is the case, the device is tested down to v cc = v bot during the production test. this guarantees that a brown-out reset will occur before v cc drops to a voltage where correct operation of the microcontroller is no longer guaranteed. the test is performed using bodlevel = 110 for atmega169v and bodlevel = 101 for atmega169l. cc table 17. bodlevel fuse coding (1) bodlevel 2..0 fuses min v bot typ v bot max v bot units 111 bod disabled 110 1.5 1.8 2.1 v 101 2.4 2.7 3.0 100 4.0 4.5 4.6 011 reserved 010 001 000 table 18. brown-out characteristics symbol parameter min typ max units v hyst brown-out detector hysteresis 50 mv t bod min pulse width on brown-out reset 2 s 40 atmega169v/l 2514j?avr?12/03 when the bod is enabled, and v cc decreases to a value below the trigger level (v bot- in figure 18), the brown-out reset is immediately activated. when v cc increases above the trigger level (v bot+ in figure 18), the delay counter starts the mcu after the time- out period t tout has expired. the bod circuit will only detect a drop in v cc if the voltage stays below the trigger level for longer than t bod given in table 16. figure 18. brown-out reset during operation watchdog reset when the watchdog times out, it will generate a short reset pulse of one ck cycle dura- tion. on the falling edge of this pulse, the delay timer starts counting the time-out period t tout . refer to page 42 for details on operation of the watchdog timer. figure 19. watchdog reset during operation mcu status register ? mcusr the mcu status register provides information on which reset source caused an mcu reset. bit 4 ? jtrf: jtag reset flag this bit is set if a reset is being caused by a logic one in the jtag reset register selected by the jtag instruction avr_reset. this bit is reset by a power-on reset, or by writing a logic zero to the flag. v cc reset time-out internal reset v bot- v bot+ t tout ck cc bit 76543210 ? ? ? jtrf wdrf borf extrf porf mcusr read/write r r r r/w r/w r/w r/w r/w initial value 0 0 0 see bit description 41 atmega169v/l 2514j?avr?12/03 bit 3 ? wdrf: watchdog reset flag this bit is set if a watchdog reset occurs. the bit is reset by a power-on reset, or by writing a logic zero to the flag. bit 2 ? borf: brown-out reset flag this bit is set if a brown-out reset occurs. the bit is reset by a power-on reset, or by writing a logic zero to the flag. bit 1 ? extrf: external reset flag this bit is set if an external reset occurs. the bit is reset by a power-on reset, or by writing a logic zero to the flag. bit 0 ? porf: power-on reset flag this bit is set if a power-on reset occurs. the bit is reset only by writing a logic zero to the flag. to make use of the reset flags to identify a reset condition, the user should read and then reset the mcusr as early as possible in the program. if the register is cleared before another reset occurs, the source of the reset can be found by examining the reset flags. internal voltage reference atmega169 features an internal bandgap referenc e. this reference is used for brown- out detection, and it can be used as an input to the analog comparator or the adc. voltage reference enable signals and start-up time the voltage reference has a start-up time that may influence the way it should be used. the start-up time is given in table 19. to save power, the reference is not always turned on. the reference is on during the following situations: 1. when the bod is enabled (by programming the bodlevel [2..0] fuse). 2. when the bandgap reference is connected to the analog comparator (by setting the acbg bit in acsr). 3. when the adc is enabled. thus, when the bod is not enabled, after setting the acbg bit or enabling the adc, the user must always allow the reference to start up before the output from the analog com- parator or adc is used. to reduce power consumption in power-down mode, the user can avoid the three conditions above to ensure that the reference is turned off before entering power-down mode. note: 1. values are guidelines only. actual values are tbd. table 19. internal voltage reference characteristics (1) symbol parameter condition min typ max units v bg bandgap reference voltage v cc = 2.7v, t a =25c 1.05 1.1 1.35 v t bg bandgap reference start-up time v cc = 2.7v, t a =25c 40 70 s i bg bandgap reference current consumption v cc = 2.7v, t a =25c 15 a 42 atmega169v/l 2514j?avr?12/03 watchdog timer the watchdog timer is clocked from a separate on-chip oscillator which runs at 1 mhz. this is the typical value at v cc = 5v. see characterization data for typical values at other v cc levels. by controlling the watchdog timer prescaler, the watchdog reset interval can be adjusted as shown in table 21 on page 43. the wdr ? watchdog reset ? instruction resets the watchdog timer. the watchdog timer is also reset when it is disabled and when a chip reset occurs. eight different clock cycle periods can be selected to determine the reset period. if the reset period expires without another watchdog reset, the atmega169 resets and executes from the reset vector. for tim- ing details on the watchdog reset, refer to table 21 on page 43. to prevent unintentional disabling of the watchdog or unintentional change of time-out period, two different safety levels are selected by the fuse wdton as shown in table 20. refer to ?timed sequences for changing the configuration of the watchdog timer? on page 44 for details. figure 20. watchdog timer table 20. wdt configuration as a function of the fuse settings of wdton wdton safety level wdt initial state how to disable the wdt how to change time-out unprogrammed 1 disabled timed sequence timed sequence programmed 2 enabled always enabled timed sequence watchdog oscillator 43 atmega169v/l 2514j?avr?12/03 watchdog timer control register ? wdtcr bits 7..5 ? res: reserved bits these bits are reserved bits in the atmega169 and will always read as zero. bit 4 ? wdce: watchdog change enable this bit must be set when the wde bit is written to logic zero. otherwise, the watchdog will not be disabled. once written to one, hardware will clear this bit after four clock cycles. refer to the description of the wde bit for a watchdog disable procedure. this bit must also be set when changing the prescaler bits. see ?timed sequences for changing the configuration of the watchdog timer? on page 44. bit 3 ? wde: watchdog enable when the wde is written to logic one, the watchdog timer is enabled, and if the wde is written to logic zero, the watchdog timer function is disabled. wde can only be cleared if the wdce bit has logic level one. to disable an enabled watchdog timer, the follow- ing procedure must be followed: 1. in the same operation, write a logic one to wdce and wde. a logic one must be written to wde even though it is set to one before the disable operation starts. 2. within the next four clock cycles, write a logic 0 to wde. this disables the watchdog. in safety level 2, it is not possible to disable the watchdog timer, even with the algo- rithm described above. see ?timed sequences for changing the configuration of the watchdog timer? on page 44. bits 2..0 ? wdp2, wdp1, wdp0: watchdog timer prescaler 2, 1, and 0 the wdp2, wdp1, and wdp0 bits determine the watchdog timer prescaling when the watchdog timer is enabled. the different prescaling values and their corresponding timeout periods are shown in table 21. bit 76543210 ? ? ? wdce wde wdp2 wdp1 wdp0 wdtcr read/write r r r r/w r/w r/w r/w r/w initial value00000000 table 21. watchdog timer prescale select wdp2 wdp1 wdp0 number of wdt oscillator cycles typical time-out at v cc = 3.0v typical time-out at v cc = 5.0v 0 0 0 16k cycles 17.1 ms 16.3 ms 0 0 1 32k cycles 34.3 ms 32.5 ms 0 1 0 64k cycles 68.5 ms 65 ms 0 1 1 128k cycles 0.14 s 0.13 s 1 0 0 256k cycles 0.27 s 0.26 s 1 0 1 512k cycles 0.55 s 0.52 s 1 1 0 1,024k cycles 1.1 s 1.0 s 1 1 1 2,048k cycles 2.2 s 2.1 s 44 atmega169v/l 2514j?avr?12/03 the following code example shows one assembly and one c function for turning off the wdt. the example assumes that interrupts are controlled (e.g. by disabling interrupts globally) so that no interrupts will occur during execution of these functions. note: 1. the example code assumes that the part specific header file is included. for i/o registers located in extended i/o ma p, ?in?, ?out?, ?sbis?, ?sbic?, ?cbi?, and ?sbi? instructions must be replaced with instructions that allow access to extended i/o. typically ?lds? and ?sts? combined with ?sbrs?, ?sbrc?, ?sbr?, and ?cbr?. timed sequences for changing the configuration of the watchdog timer the sequence for changing configuration differs slightly between the two safety levels. separate procedures are described for each level. safety level 1 in this mode, the watchdog timer is initially disabled, but can be enabled by writing the wde bit to 1 without any restriction. a timed sequence is needed when changing the watchdog time-out period or disabling an enabled watchdog timer. to disable an enabled watchdog timer, and/or changing the watchdog time-out, the following proce- dure must be followed: 1. in the same operation, write a logic one to wdce and wde. a logic one must be written to wde regardless of the previous value of the wde bit. 2. within the next four clock cycles, in the same operation, write the wde and wdp bits as desired, but with the wdce bit cleared. safety level 2 in this mode, the watchdog timer is always enabled, and the wde bit will always read as one. a timed sequence is needed when changing the watchdog time-out period. to change the watchdog time-out, the following procedure must be followed: assembly code example (1) wdt_off: ; reset wdt wdr ; write logical one to wdce and wde in r16, wdtcr ori r16, (1< 46 atmega169v/l 2514j?avr?12/03 interrupts this section describes the specifics of the interrupt handling as performed in atmega169. for a general explanation of the avr interrupt handling, refer to ?reset and interrupt handling? on page 12. interrupt vectors in atmega169 notes: 1. when the bootrst fuse is programmed, the device will jump to the boot loader address at reset, see ?boot loader support ? read-while-write self-programming? on page 252. 2. when the ivsel bit in mcucr is set, interrupt vectors will be moved to the start of the boot flash section. the address of eac h interrupt vector will then be the address in this table added to the start address of the boot flash section. table 22. reset and interrupt vectors vector no. program address (2) source interrupt definition 1 0x0000 (1) reset external pin, power-on reset, brown-out reset, watchdog reset, and jtag avr reset 2 0x0002 int0 external interrupt request 0 3 0x0004 pcint0 pin change interrupt request 0 4 0x0006 pcint1 pin change interrupt request 1 5 0x0008 timer2 comp timer/counter2 compare match 6 0x000a timer2 ovf timer/counter2 overflow 7 0x000c timer1 capt timer/counter1 capture event 8 0x000e timer1 compa timer/counter1 compare match a 9 0x0010 timer1 compb timer/counter1 compare match b 10 0x0012 timer1 ovf timer/counter1 overflow 11 0x0014 timer0 comp timer/counter0 compare match 12 0x0016 timer0 ovf timer/counter0 overflow 13 0x0018 spi, stc spi serial transfer complete 14 0x001a usart, rx usart, rx complete 15 0x001c usart, udre usart data register empty 16 0x001e usart, tx usart, tx complete 17 0x0020 usi start usi start condition 18 0x0022 usi overflow usi overflow 19 0x0024 analog comp analog comparator 20 0x0026 adc adc conversion complete 21 0x0028 ee ready eeprom ready 22 0x002a spm ready store program memory ready 23 0x002c lcd lcd start of frame 47 atmega169v/l 2514j?avr?12/03 table 23 shows reset and interrupt vectors placement for the various combinations of bootrst and ivsel settings. if the program never enables an interrupt source, the interrupt vectors are not used, and regular program code can be placed at these loca- tions. this is also the case if the reset vector is in the application section while the interrupt vectors are in the boot section or vice versa. note: 1. the boot reset address is shown in table 113 on page 264. for the bootrst fuse ?1? means unprogrammed while ?0? means programmed. the most typical and general program setup for the reset and interrupt vector addresses in atmega169 is: address labels code comments 0x0000 jmp reset ; reset handler 0x0002 jmp ext_int0 ; irq0 handler 0x0004 jmp pcint0 ; pcint0 handler 0x0006 jmp pcint1 ; pcint0 handler 0x0008 jmp tim2_comp ; timer2 compare handler 0x000a jmp tim2_ovf ; timer2 overflow handler 0x000c jmp tim1_capt ; timer1 capture handler 0x000e jmp tim1_compa ; timer1 comparea handler 0x0010 jmp tim1_compb ; timer1 compareb handler 0x0012 jmp tim1_ovf ; timer1 overflow handler 0x0014 jmp tim0_comp ; timer0 compare handler 0x0016 jmp tim0_ovf ; timer0 overflow handler 0x0018 jmp spi_stc ; spi transfer complete handler 0x001a jmp usart_rxc ; usart rx complete handler 0x001c jmp usart_dre ; usart,udr empty handler 0x001e jmp usart_txc ; usart tx complete handler 0x0020 jmp usi_strt ; usi start condition handler 0x0022 jmp usi_ovfl ; usi overflow handler 0x0024 jmp ana_comp ; analog comparator handler 0x0026 jmp adc ; adc conversion complete handler 0x0028 jmp ee_rdy ; eeprom ready handler 0x002a jmp spm_rdy ; spm ready handler 0x002c jmp lcd_sof ; lcd start of frame handler ; 0x002e reset: ldi r16, high(ramend); main program start 0x002f out sph,r16 set stack pointer to top of ram 0x0030 ldi r16, low(ramend) 0x0031 out spl,r16 0x0032 sei ; enable interrupts 0x0033 48 atmega169v/l 2514j?avr?12/03 when the bootrst fuse is unprogrammed, the boot section size set to 2k bytes and the ivsel bit in the mcucr register is set before any interrupts are enabled, the most typical and general program setup for the reset and interrupt vector addresses is: address labels code comments 0x0000 reset: ldi r16,high(ramend) ; main program start 0x0001 out sph,r16 ; set stack pointer to top of ram 0x0002 ldi r16,low(ramend) 0x0003 out spl,r16 0x0004 sei ; enable interrupts 0x0005 49 atmega169v/l 2514j?avr?12/03 when the bootrst fuse is programmed, the boot section size set to 2k bytes and the ivsel bit in the mcucr register is set before any interrupts are enabled, the most typ- ical and general program setup for the reset and interrupt vector addresses is: address labels code comments ; .org 0x1c00 0x1c00 jmp reset ; reset handler 0x1c02 jmp ext_int0 ; irq0 handler 0x1c04 jmp pcint0 ; pcint0 handler ... ... ... ; 0x1c2c jmp spm_rdy ; store program memory ready handler ; 0x1c2e reset: ldi r16,high(ramend) ; main program start 0x1c2f out sph,r16 ; set stack pointer to top of ram 0x1c30 ldi r16,low(ramend) 0x1c31 out spl,r16 0x1c32 sei ; enable interrupts 0x1c33 50 atmega169v/l 2514j?avr?12/03 bit 0 ? ivce: interrupt vector change enable the ivce bit must be written to logic one to enable change of the ivsel bit. ivce is cleared by hardware four cycles after it is written or when ivsel is written. setting the ivce bit will disable interrupts, as explained in the ivsel description above. see code example below. assembly code example move_interrupts: ; enable change of interrupt vectors ldi r16, (1< 52 atmega169v/l 2514j?avr?12/03 note that enabling the alternate function of some of the port pins does not affect the use of the other pins in the port as general digital i/o. ports as general digital i/o the ports are bi-directional i/o ports with optional internal pull-ups. figure 22 shows a functional description of one i/o-port pin, here generically called pxn. figure 22. general digital i/o (1) note: 1. wrx, wpx, wdx, rrx, rpx, and rdx are common to all pins within the same port. clk i/o , sleep, and pud are common to all ports. configuring the pin each port pin consists of three register bits: ddxn, portxn, and pinxn. as shown in ?register description for i/o-ports? on page 73, the ddxn bits are accessed at the ddrx i/o address, the portxn bits at the portx i/o address, and the pinxn bits at the pinx i/o address. the ddxn bit in the ddrx register selects the direction of this pin. if ddxn is written logic one, pxn is configured as an output pin. if ddxn is written logic zero, pxn is config- ured as an input pin. if portxn is written logic one when the pin is configured as an input pin, the pull-up resistor is activated. to switch the pull-up resistor off, portxn has to be written logic zero or the pin has to be configured as an output pin. the port pins are tri-stated when reset condition becomes active, even if no clocks are running. if portxn is written logic one when the pin is configured as an output pin, the port pin is driven high (one). if portxn is written logic zero when the pin is configured as an out- put pin, the port pin is driven low (zero). clk rpx rrx rdx wdx pud synchronizer wdx: write ddrx wrx: write portx rrx: read portx register rpx: read portx pin pud: pullup disable clk i/o : i/o clock rdx: read ddrx d l q q reset reset q q d q q d clr portxn q q d clr ddxn pinxn data b u s sleep sleep: sleep control pxn i/o wpx 0 1 wrx wpx: write pinx register 53 atmega169v/l 2514j?avr?12/03 toggling the pin writing a logic one to pinxn toggles the value of portxn, independent on the value of ddrxn. note that the sbi instruction can be used to toggle one single bit in a port. switching between input and output when switching between tri-state ({ddxn, portxn} = 0b00) and output high ({ddxn, portxn} = 0b11), an intermediate state with either pull-up enabled {ddxn, portxn} = 0b01) or output low ({ddxn, portxn} = 0b10) must occur. normally, the pull-up enabled state is fully acceptable, as a high-impedant environment will not notice the dif- ference between a strong high driver and a pull-up. if this is not the case, the pud bit in the mcucr register can be set to disable all pull-ups in all ports. switching between input with pull-up and output low generates the same problem. the user must use either the tri-state ({ddxn, portxn} = 0b00) or the output high state ({ddxn, portxn} = 0b11) as an intermediate step. table 24 summarizes the control signals for the pin value. reading the pin value independent of the setting of data direction bit ddxn, the port pin can be read through the pinxn register bit. as shown in figure 22, the pinxn register bit and the preceding latch constitute a synchronizer. this is needed to avoid metastability if the physical pin changes value near the edge of the internal clock, but it also introduces a delay. figure 23 shows a timing diagram of the synchronization when reading an externally applied pin value. the maximum and minimum propagation delays are denoted t pd,max and t pd,min respectively. figure 23. synchronization when reading an externally applied pin value table 24. port pin configurations ddxn portxn pud (in mcucr) i/o pull-up comment 0 0 x input no tri-state (hi-z) 0 1 0 input yes pxn will source current if ext. pulled low. 0 1 1 input no tri-state (hi-z) 1 0 x output no output low (sink) 1 1 x output no output high (source) xxx in r17, pinx 0x00 0xff instructions sync latch pinxn r17 xxx system clk t pd, max t pd, min 54 atmega169v/l 2514j?avr?12/03 consider the clock period starting shortly after the first falling edge of the system clock. the latch is closed when the clock is low, and goes transparent when the clock is high, as indicated by the shaded region of the ?sync latch? signal. the signal value is latched when the system clock goes low. it is clocked into the pinxn register at the suc- ceeding positive clock edge. as indicated by the two arrows tpd,max and tpd,min, a single signal transition on the pin will be delayed between ? and 1? system clock period depending upon the time of assertion. when reading back a software assigned pin value, a nop instruction must be inserted as indicated in figure 24. the out instruction sets the ?sync latch? signal at the positive edge of the clock. in this case, the delay tpd through the synchronizer is 1 system clock period. figure 24. synchronization when reading a software assigned pin value out portx, r16 nop in r17, pinx 0xff 0x00 0xff system clk r16 instructions sync latch pinxn r17 t pd 55 atmega169v/l 2514j?avr?12/03 the following code example shows how to set port b pins 0 and 1 high, 2 and 3 low, and define the port pins from 4 to 7 as input with pull-ups assigned to port pins 6 and 7. the resulting pin values are read back again, but as previously discussed, a nop instruction is included to be able to read back the value recently assigned to some of the pins. note: 1. for the assembly program, two temporary registers are used to minimize the time from pull-ups are set on pins 0, 1, 6, and 7, until the direction bits are correctly set, defining bit 2 and 3 as low and redefining bits 0 and 1 as strong high drivers. digital input enable and sleep modes as shown in figure 22, the digital input signal can be clamped to ground at the input of the schmitt trigger. the signal denoted sleep in the figure, is set by the mcu sleep controller in power-down mode, power-save mode, and standby mode to avoid high power consumption if some input signals are left floating, or have an analog signal level close to v cc /2. sleep is overridden for port pins enabled as external interrupt pins. if the external inter- rupt request is not enabled, sleep is active also for these pins. sleep is also overridden by various other alternate functions as described in ?alternate port func- tions? on page 56. if a logic high level (?one?) is present on an asynchronous external interrupt pin config- ured as ?interrupt on rising edge, falling edge, or any logic change on pin? while the external interrupt is not enabled, the corresponding external interrupt flag will be set when resuming from the above mentioned sleep mode, as the clamping in these sleep mode produces the requested logic change. assembly code example (1) ... ; define pull-ups and set outputs high ; define directions for port pins ldi r16,(1< 57 atmega169v/l 2514j?avr?12/03 figure 25. alternate port functions (1) note: 1. wrx, wpx, wdx, rrx, rpx, and rdx are common to all pins within the same port. clk i/o , sleep, and pud are common to all ports. all other signals are unique for each pin. clk rpx rrx wrx rdx wdx pud synchronizer wdx: write ddrx wrx: write portx rrx: read portx register rpx: read portx pin pud: pullup disable clk i/o : i/o clock rdx: read ddrx d l q q set clr 0 1 0 1 0 1 dixn aioxn dieoexn pvovxn pvoexn ddovxn ddoexn puoexn puovxn puoexn: pxn pull-up override enable puovxn: pxn pull-up override value ddoexn: pxn data direction override enable ddovxn: pxn data direction override value pvoexn: pxn port value override enable pvovxn: pxn port value override value dixn: digital input pin n on portx aioxn: analog input/output pin n on portx reset reset q q d clr q q d clr q q d clr pinxn portxn ddxn data b u s 0 1 dieovxn sleep dieoexn: pxn digital input-enable override enable dieovxn: pxn digital input-enable override value sleep: sleep control pxn i/o 0 1 ptoexn wpx ptoexn: pxn, port toggle override enable wpx: write pinx 58 atmega169v/l 2514j?avr?12/03 table 25 summarizes the function of the overriding signals. the pin and port indexes from figure 25 are not shown in the succeeding tables. the overriding signals are gen- erated internally in the modules having the alternate function. the following subsections shortly describe the alternate functions for each port, and relate the overriding signals to the alternate function. refer to the alternate function description for further details. table 25. generic description of overriding signals for alternate functions signal name full name description puoe pull-up override enable if this signal is set, the pull-up enable is controlled by the puov signal. if this signal is cleared, the pull-up is enabled when {ddxn, portxn, pud} = 0b010. puov pull-up override value if puoe is set, the pull-up is enabled/disabled when puov is set/cleared, regardless of the setting of the ddxn, portxn, and pud register bits. ddoe data direction override enable if this signal is set, the output driver enable is controlled by the ddov signal. if this signal is cleared, the output driver is enabled by the ddxn register bit. ddov data direction override value if ddoe is set, the output driver is enabled/disabled when ddov is set/cleared, regardless of the setting of the ddxn register bit. pvoe port value override enable if this signal is set and the output driver is enabled, the port value is controlled by the pvov signal. if pvoe is cleared, and the output driver is enabled, the port value is controlled by the portxn register bit. pvov port value override value if pvoe is set, the port value is set to pvov, regardless of the setting of the portxn register bit. ptoe port toggle override enable if ptoe is set, the portxn register bit is inverted. dieoe digital input enable override enable if this bit is set, the digital input enable is controlled by the dieov signal. if this signal is cleared, the digital input enable is determined by mcu state (normal mode, sleep mode). dieov digital input enable override value if dieoe is set, the digital input is enabled/disabled when dieov is set/cleared, regardless of the mcu state (normal mode, sleep mode). di digital input this is the digital input to alternate functions. in the figure, the signal is connected to the output of the schmitt trigger but before the synchronizer. unless the digital input is used as a clock source, the module with the alternate function will use its own synchronizer. aio analog input/output this is the analog input/output to/from alternate functions. the signal is connected directly to the pad, and can be used bi-directionally. 59 atmega169v/l 2514j?avr?12/03 mcu control register ? mcucr bit 4 ? pud: pull-up disable when this bit is written to one, the pull-ups in the i/o ports are disabled even if the ddxn and portxn registers are configured to enable the pull-ups ({ddxn, portxn} = 0b01). see ?configuring the pin? on page 52 for more details about this feature. alternate functions of port a the port a has an alternate function as com0:3 and seg0:3 for the lcd controller. table 27 and table 28 relates the alternate functions of port a to the overriding signals shown in figure 25 on page 57. bit 7 6 5 4 3 2 1 0 jtd ? ?pud ? ? ivsel ivce mcucr read/write r/w r r r/w r r r/w r/w initial value 0 0 0 0 0 0 0 0 table 26. port a pins alternate functions port pin alternate function pa7 seg3 (lcd front plane 3) pa6 seg2 (lcd front plane 2) pa5 seg1 (lcd front plane 1) pa4 seg0 (lcd front plane 0) pa3 com3 (lcd back plane 3) pa2 com2 (lcd back plane 2) pa1 com1 (lcd back plane 1) pa0 com0 (lcd back plane 0) table 27. overriding signals for alternate functions in pa7..pa4 signal name pa7/seg3 pa6/seg2 pa5/seg1 pa4/seg0 puoe lcden lcden lcden lcden puov0000 ddoe lcden lcden lcden lcden ddov0000 pvoe0000 pvov0000 ptoe???? dieoe lcden lcden lcden lcden dieov0000 di ???? aio seg3 seg2 seg1 seg0 60 atmega169v/l 2514j?avr?12/03 alternate functions of port b the port b pins with alternate functions are shown in table 29. the alternate pin configuration is as follows: oc2a/pcint15, bit 7 oc2, output compare match a output: the pb7 pin can serve as an external output for the timer/counter2 output compare a. the pin has to be configured as an output (ddb7 set (one)) to serve this function. the oc2a pin is also the output pin for the pwm mode timer function. pcint15, pin change interrupt source 15: the pb7 pin can serve as an external inter- rupt source. table 28. overriding signals for alternate functions in pa3..pa0 signal name pa3/com3 pa2/com2 pa1/com1 pa0/com0 puoe lcden (lcdmux>2) lcden (lcdmux>1) lcden (lcdmux>0) lcden puov0000 ddoe lcden (lcdmux>2) lcden (lcdmux>1) lcden (lcdmux>0) lcden ddov0000 pvoe0000 pvov0000 ptoe???? dieoe lcden (lcdmux>2) lcden (lcdmux>1) lcden (lcdmux>0) lcden dieov0000 di???? aio com3 com2 com1 com0 table 29. port b pins alternate functions port pin alternate functions pb7 oc2a/pcint15 (output compare and pwm output a for timer/counter2 or pin change interrupt15). pb6 oc1b/pcint14 (output compare and pwm output b for timer/counter1 or pin change interrupt14). pb5 oc1a/pcint13 (output compare and pwm output a for timer/counter1 or pin change interrupt13). pb4 oc0a/pcint12 (output compare and pwm output a for timer/counter0 or pin change interrupt12). pb3 miso/pcint11 (spi bus master input/slave output or pin change interrupt11). pb2 mosi/pcint10 (spi bus master output/slave input or pin change interrupt10). pb1 sck/pcint9 (spi bus serial clock or pin change interrupt9). pb0 ss /pcint8 (spi slave select input or pin change interrupt8). 61 atmega169v/l 2514j?avr?12/03 oc1b/pcint14, bit 6 oc1b, output compare match b output: the pb6 pin can serve as an external output for the timer/counter1 output compare b. the pin has to be configured as an output (ddb6 set (one)) to serve this function. the oc1b pin is also the output pin for the pwm mode timer function. pcint14, pin change interrupt source 14: the pb6 pin can serve as an external inter- rupt source. oc1a/pcint13, bit 5 oc1a, output compare match a output: the pb5 pin can serve as an external output for the timer/counter1 output compare a. the pin has to be configured as an output (ddb5 set (one)) to serve this function. the oc1a pin is also the output pin for the pwm mode timer function. pcint13, pin change interrupt source 13: the pb5 pin can serve as an external inter- rupt source. oc0a/pcint12, bit 4 oc0a, output compare match a output: the pb4 pin can serve as an external output for the timer/counter0 output compare a. the pin has to be configured as an output (ddb4 set (one)) to serve this function. the oc0a pin is also the output pin for the pwm mode timer function. pcint12, pin change interrupt source 12: the pb4 pin can serve as an external inter- rupt source. miso/pcint11 ? port b, bit 3 miso: master data input, slave data output pin for spi channel. when the spi is enabled as a master, this pin is configured as an input regardless of the setting of ddb3. when the spi is enabled as a slave, the data direction of this pin is controlled by ddb3. when the pin is forced to be an input, the pull-up can still be controlled by the portb3 bit. pcint11, pin change interrupt source 11: the pb3 pin can serve as an external inter- rupt source. mosi/pcint10 ? port b, bit 2 mosi: spi master data output, slave data input for spi channel. when the spi is enabled as a slave, this pin is configured as an input regardless of the setting of ddb2. when the spi is enabled as a master, the data direction of this pin is controlled by ddb2. when the pin is forced to be an input, the pull-up can still be controlled by the portb2 bit. pcint10, pin change interrupt source 10: the pb2 pin can serve as an external inter- rupt source. 62 atmega169v/l 2514j?avr?12/03 sck/pcint9 ? port b, bit 1 sck: master clock output, slave clock input pin for spi channel. when the spi is enabled as a slave, this pin is configured as an input regardless of the setting of ddb1. when the spi is enabled as a master, the data direction of this pin is controlled by ddb1. when the pin is forced to be an input, the pull-up can still be controlled by the portb1 bit. pcint9, pin change interrupt source 9: the pb1 pin can serve as an external interrupt source. ss /pcint8 ? port b, bit 0 ss : slave port select input. when the spi is enabled as a slave, this pin is configured as an input regardless of the setting of ddb0. as a slave, the spi is activated when this pin is driven low. when the spi is enabled as a master, the data direction of this pin is controlled by ddb0. when the pin is forced to be an input, the pull-up can still be con- trolled by the portb0 bit pcint8, pin change interrupt source 8: the pb0 pin can serve as an external interrupt source. table 30 and table 31 relate the alternate functions of port b to the overriding signals shown in figure 25 on page 57. spi mstr input and spi slave output constitute the miso signal, while mosi is divided into spi mstr output and spi slave input. table 30. overriding signals for alternate functions in pb7..pb4 signal name pb7/oc2a/ pcint15 pb6/oc1b/ pcint14 pb5/oc1a/ pcint13 pb4/oc0a/ pcint12 puoe 0 0 0 0 puov 0 0 0 0 ddoe 0 0 0 0 ddov 0 0 0 0 pvoe oc2a enable oc1b enable oc1a enable oc0a enable pvov oc2a oc1b oc1a oc0a ptoe ? ? ? ? dieoe pcint15 pcie1 pcint14 pcie1 pcint13 pcie1 pcint12 pcie1 dieov 1 1 1 1 di pcint15 input pcint14 input pcint13 input pcint12 input aio ? ? ? ? 63 atmega169v/l 2514j?avr?12/03 alternate functions of port c the port c has an alternate function as the seg5:12 for the lcd controller table 31. overriding signals for alternate functions in pb3..pb0 signal name pb3/miso/ pcint11 pb2/mosi/ pcint10 pb1/sck/ pcint9 pb0/ss / pcint8 puoe spe mstr spe mstr spe mstr spe mstr puov portb3 pud portb2 pud portb1 pud portb0 pud ddoe spe mstr spe mstr spe mstr spe mstr ddov 0 0 0 0 pvoe spe mstr spe mstr spe mstr 0 pvov spi slave output spi mstr output sck output 0 ptoe ? ? ? ? dieoe pcint11 pcie1 pcint10 pcie1 pcint9 pcie1 pcint8 pcie1 dieov 1 1 1 1 di pcint11 input spi mstr input pcint10 input spi slave input pcint9 input sck input pcint8 input spi ss aio ? ? ? ? table 32. port c pins alternate functions port pin alternate function pc7 seg5 (lcd front plane 5) pc6 seg6 (lcd front plane 6) pc5 seg7 (lcd front plane 7) pc4 seg8 (lcd front plane 8) pc3 seg9 (lcd front plane 9) pc2 seg10 (lcd front plane 10) pc1 seg11 (lcd front plane 11) pc0 seg12 (lcd front plane 12) 64 atmega169v/l 2514j?avr?12/03 table 33 and table 34 relate the alternate functions of port c to the overriding signals shown in figure 25 on page 57. table 33. overriding signals for alternate functions in pc7..pc4 signal name pc7/seg5 pc6/seg6 pc5/seg7 pc4/seg8 puoe lcden lcden lcden lcden puov0000 ddoe lcden lcden lcden lcden ddov0000 pvoe0000 pvov0000 ptoe???? dieoe lcden lcden lcden lcden dieov0000 di???? aio seg5 seg6 seg7 seg8 table 34. overriding signals for alternate functions in pc3..pc0 signal name pc3/seg9 pc2/seg10 pc1/seg11 pc0/seg12 puoe lcden lcden lcden lcden puov 0 0 0 0 ddoe lcden lcden lcden lcden ddov 0 0 0 0 pvoe 0 0 0 0 pvov 0 0 0 0 ptoe ? ? ? ? dieoe lcden lcden lcden lcden dieov 0 0 0 0 di ? ? ? ? aio seg9 seg10 seg11 seg12 65 atmega169v/l 2514j?avr?12/03 alternate functions of port d the port d pins with alternate functions are shown in table 35. the alternate pin configuration is as follows: seg15 - seg20 ? port d, bit 7:2 seg15-seg20, lcd front plane 15-20. int0/seg21 ? port d, bit 1 int0, external interrupt source 0. the pd1 pin can serve as an external interrupt source to the mcu. seg21, lcd front plane 21. icp1/seg22 ? port d, bit 0 icp1 ? input capture pin1: the pd0 pin can act as an input capture pin for timer/counter1. seg22, lcd front plane 22 table 35. port d pins alternate functions port pin alternate function pd7 seg15 (lcd front plane 15) pd6 seg16 (lcd front plane 16) pd5 seg17 (lcd front plane 17) pd4 seg18 (lcd front plane 18) pd3 seg19 (lcd front plane 19) pd2 seg20 (lcd front plane 20) pd1 int0/seg21 (external interrupt0 input or lcd front plane 21) pd0 icp1/seg22 (timer/counter1 input capture pin or lcd front plane 22) 66 atmega169v/l 2514j?avr?12/03 table 36 and table 37 relates the alternate functions of port d to the overriding signals shown in figure 25 on page 57. table 36. overriding signals for alternate functions pd7..pd4 signal name pd7/seg15 pd6/seg16 pd5/seg17 pd4/seg18 puoe lcden (lcdpm>1) lcden (lcdpm>1) lcden (lcdpm>2) lcden (lcdpm>2) puov0000 ddoe lcden (lcdpm>1) lcden (lcdpm>1) lcden (lcdpm>2) lcden (lcdpm>2) ddov0000 pvoe0000 pvov0000 ptoe???? dieoe lcden (lcdpm>1) lcden (lcdpm>1) lcden (lcdpm>2) lcden (lcdpm>2) dieov0000 di???? aio seg15 seg16 seg17 seg18 table 37. overriding signals for alternate functions in pd3..pd0 signal name pd3/seg19 pd2/seg20 pd1/int0/seg21 pd0/icp1/seg22 puoe lcden (lcdpm>3) lcden (lcdpm>3) lcden (lcdpm>4) lcden (lcdpm>4) puov 0 0 0 0 ddoe lcden (lcdpm>3) lcden (lcdpm>3) lcden (lcdpm>4) lcden (lcdpm>4) ddov 0 0 0 0 pvoe 0 0 0 0 pvov 0 0 0 0 ptoe ? ? ? ? dieoe lcden (lcdpm>3) lcden (lcdpm>3) lcden + (int0 enable) lcden (lcdpm>4) dieov 0 0 lcden (int0 enable) 0 di ? ? int0 input icp1 input aio ? ? 67 atmega169v/l 2514j?avr?12/03 alternate functions of port e the port e pins with alternate functions are shown in table 38. pcint7 ? port e, bit 7 pcint7, pin change interrupt source 7: the pe7 pin can serve as an external interrupt source. clko, divided system clock: the divided system clock can be output on the pe7 pin. the divided system clock will be output if the ckout fuse is programmed, regardless of the porte7 and dde7 settings. it will also be output during reset. do/pcint6 ? port e, bit 6 do, universal serial interface data output. pcint6, pin change interrupt source 6: the pe6 pin can serve as an external interrupt source. di/sda/pcint5 ? port e, bit 5 di, universal serial interface data input. sda, two-wire serial interface data: pcint5, pin change interrupt source 5: the pe5 pin can serve as an external interrupt source. usck/scl/pcint4 ? port e, bit 4 usck, universal serial interface clock. scl, two-wire serial interface clock. pcint4, pin change interrupt source 4: the pe4 pin can serve as an external interrupt source. ain1/pcint3 ? port e, bit 3 ain1 ? analog comparator negative input. this pin is directly connected to the negative input of the analog comparator. pcint3, pin change interrupt source 3: the pe3 pin can serve as an external interrupt source. table 38. port e pins alternate functions port pin alternate function pe7 pcint7 (pin change interrupt7) clko (divided system clock) pe6 do/pcint6 (usi data output or pin change interrupt6) pe5 di/sda/pcint5 (usi data input or twi serial data or pin change interrupt5) pe4 usck/scl/pcint4 (usart external clock input/output or twi serial clock or pin change interrupt4) pe3 ain1/pcint3 (analog comparator negative input or pin change interrupt3) pe2 xck/ain0/ pcint2 (usart external clock or analog comparator positive input or pin change interrupt2) pe1 txd/pcint1 (usart transmit pin or pin change interrupt1) pe0 rxd/pcint0 (usart receive pin or pin change interrupt0) 68 atmega169v/l 2514j?avr?12/03 xck/ain0/pcint2 ? port e, bit 2 xck, usart external clock. the data direction register (dde2) controls whether the clock is output (dde2 set) or input (dde2 cleared). the xck pin is active only when the usart operates in synchronous mode. ain0 ? analog comparator positive input. this pin is directly connected to the positive input of the analog comparator. pcint2, pin change interrupt source 2: the pe2 pin can serve as an external interrupt source. txd/pcint1 ? port e, bit 1 txd0, uart0 transmit pin. pcint1, pin change interrupt source 1: the pe1 pin can serve as an external interrupt source. rxd/pcint0 ? port e, bit 0 rxd, usart receive pin. receive data (data input pin for the usart). when the usart receiver is enabled this pin is configured as an input regardless of the value of dde0. when the usart forces this pin to be an input, a logical one in porte0 will turn on the internal pull-up. pcint0, pin change interrupt source 0: the pe0 pin can serve as an external interrupt source. table 39 and table 40 relates the alternate functions of port e to the overriding signals shown in figure 25 on page 57. note: 1. ckout is one if the ckout fuse is programmed table 39. overriding signals for alternate functions pe7..pe4 signal name pe7/pcint7 pe6/do/ pcint6 pe5/di/sda/ pcint5 pe4/usck/scl/ pcint4 puoe 0 0 usi_two-wire 0 puov 0 0 0 0 ddoe ckout (1) 0 usi_two-wire usi_two-wire ddov 1 0 (sda + porte5 ) dde5 (usi_scl_hold + porte4 ) + dde4 pvoe ckout (1) usi_three- wire usi_two-wire dde5 usi_two-wire dde4 pvov clk i/o do 0 0 ptoe ? ? ? usitc dieoe pcint7 pcie0 pcint6 pcie0 (pcint5 pcie0) + usisie (pcint4 pcie0) + usisie dieov 1 1 1 1 di pcint7 input pcint6 input di/sda input pcint5 input usckl/scl input pcint4 input aio ? ? ? ? 69 atmega169v/l 2514j?avr?12/03 note: 1. ain0d and ain1d is described in ?digital input disable register 1 ? didr1? on page 191. alternate functions of port f the port f has an alternate function as analog input for the adc as shown in table 41. if some port f pins are configured as outputs, it is essential that these do not switch when a conversion is in progress. this might corrupt the result of the conversion. if the jtag interface is enabled, the pull-up resistors on pins pf7(tdi), pf5(tms) and pf4(tck) will be activated even if a reset occurs. tdi, adc7 ? port f, bit 7 adc7, analog to digital converter, channel 7 . tdi, jtag test data in: serial input data to be shifted in to the instruction register or data register (scan chains). when the jtag interface is enabled, this pin can not be used as an i/o pin. table 40. overriding signals for alternate functions in pe3..pe0 signal name pe3/ain1/ pcint3 pe2/xck/ain0/ pcint2 pe1/txd/ pcint1 pe0/rxd/pcint0 puoe 0 0 txen rxen puov 0 0 0 porte0 pud ddoe 0 0 txen rxen ddov 0 0 1 0 pvoe 0 xck output enable txen 0 pvov 0 xck txd 0 ptoe ? ? ? ? dieoe (pcint3 pcie0) + ain1d (1) (pcint2 pcie0) + ain0d (1) pcint1 pcie0 pcint0 pcie0 dieov pcint3 pcie0 pcint2 pcie0 1 1 di pcint3 input xck/pcint2 input pcint1 input rxd/pcint0 input aio ain1 input ain0 input ? ? table 41. port f pins alternate functions port pin alternate function pf7 adc7/tdi (adc input channel 7 or jtag test data input) pf6 adc6/tdo (adc input channel 6 or jtag test data output) pf5 adc5/tms (adc input channel 5 or jtag test mode select) pf4 adc4/tck (adc input channel 4 or jtag test clock) pf3 adc3 (adc input channel 3) pf2 adc2 (adc input channel 2) pf1 adc1 (adc input channel 1) pf0 adc0 (adc input channel 0) 70 atmega169v/l 2514j?avr?12/03 tdo, adc6 ? port f, bit 6 adc6, analog to digital converter, channel 6 . tdo, jtag test data out: serial output data from instruction register or data regis- ter. when the jtag interface is enabled, this pin can not be used as an i/o pin. in tap states that shift out data, the tdo pin drives actively. in other states the pin is pulled high. tms, adc5 ? port f, bit 5 adc5, analog to digital converter, channel 5 . tms, jtag test mode select: this pin is used for navigating through the tap-controller state machine. when the jtag interface is enabled, this pin can not be used as an i/o pin. tck, adc4 ? port f, bit 4 adc4, analog to digital converter, channel 4 . tck, jtag test clock: jtag operation is synchronous to tck. when the jtag inter- face is enabled, this pin can not be used as an i/o pin. adc3 - adc0 ? port f, bit 3:0 analog to digital converter, channel 3-0. table 42. overriding signals for alternate functions in pf7..pf4 signal name pf7/adc7/tdi pf6/adc6/tdo pf5/adc5/tms pf4/adc4/tck puoe jtagen jtagen jtagen jtagen puov 1 1 1 1 ddoe jtagen jtagen jtagen jtagen ddov 0 shift_ir + shift_dr 00 pvoe 0 jtagen 0 0 pvov 0 tdo 0 0 ptoe ? ? ? ? dieoe jtagen jtagen jtagen jtagen dieov 0 0 0 0 di ? ? ? ? aio tdi adc7 input adc6 input tms adc5 input tck adc4 input 71 atmega169v/l 2514j?avr?12/03 alternate functions of port g the alternate pin configuration is as follows: the alternate pin configuration is as follows: t0/seg23 ? port g, bit 4 t0, timer/counter0 counter source. seg23, lcd front plane 23 t1/seg24 ? port g, bit 3 t1, timer/counter1 counter source. seg24, lcd front plane 24 seg4 ? port g, bit 2 seg4, lcd front plane 4 seg13 ? port g, bit 1 seg13, segment driver 13 seg14 ? port g, bit 0 seg14, lcd front plane 14 table 43. overriding signals for alternate functions in pf3..pf0 signal name pf3/adc3 pf2/adc2 pf1/adc1 pf0/adc0 puoe0000 puov0000 ddoe0000 ddov0000 pvoe0000 pvov0000 ptoe???? dieoe0000 dieov0000 di???? aio adc3 input adc2 input adc1 input adc0 input table 44. port g pins alternate functions port pin alternate function pg4 t0/seg23 (timer/counter0 clock input or lcd front plane 23) pg3 t1/seg24 (timer/counter1 clock input or lcd front plane 24) pg2 seg4 (lcd front plane 4) pg1 seg13 (lcd front plane 13) pg0 seg14 (lcd front plane 14) 72 atmega169v/l 2514j?avr?12/03 table 44 and table 45 relates the alternate functions of port g to the overriding signals shown in figure 25 on page 57. table 45. overriding signals for alternate functions in pg4 signal name pg4/t0/seg23 puoe lcden (lcdpm>5) puov 0 ddoe lcden (lcdpm>5) ddov 1 pvoe 0 pvov 0 ptoe ? ? ? ? dieoe lcden (lcdpm>5) dieov 0 di t0 input aio seg23 table 46. overriding signals for alternate functions in pg3:0 signal name pg3/t1/seg24 pg2/seg4 pg1/seg13 pg0/seg14 puoe lcden (lcdpm>6) lcden lcden (lcdpm>0) lcden (lcdpm>0) puov 0 0 0 0 ddoe lcden (lcdpm>6) lcden lcden (lcdpm>0) lcden (lcdpm>0) ddov 0 0 0 0 pvoe 0 0 0 0 pvov 0 0 0 0 ptoe ? ? ? ? dieoe lcden (lcdpm>6) lcden lcden (lcdpm>0) lcden (lcdpm>0) dieov 0 0 0 0 di t1 input ? ? ? aio seg24 seg4 seg13 seg14 73 atmega169v/l 2514j?avr?12/03 register description for i/o-ports port a data register ? porta port a data direction register ? ddra port a input pins address ? pina port b data register ? portb port b data direction register ? ddrb port b input pins address ? pinb port c data register ? portc port c data direction register ? ddrc bit 76543210 porta7 porta6 porta5 porta4 porta3 porta2 porta1 porta0 porta read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 dda7 dda6 dda5 dda4 dda3 dda2 dda1 dda0 ddra read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 pina7 pina6 pina5 pina4 pina3 pina2 pina1 pina0 pina read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value n/a n/a n/a n/a n/a n/a n/a n/a bit 76543210 portb7 portb6 portb5 portb4 portb3 portb2 portb1 portb0 portb read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 ddb7 ddb6 ddb5 ddb4 ddb3 ddb2 ddb1 ddb0 ddrb read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 pinb7 pinb6 pinb5 pinb4 pinb3 pinb2 pinb1 pinb0 pinb read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value n/a n/a n/a n/a n/a n/a n/a n/a bit 76543210 portc7 portc6 portc5 portc4 portc3 portc2 portc1 portc0 portc read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 ddc7 ddc6 ddc5 ddc4 ddc3 ddc2 ddc1 ddc0 ddrc read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 74 atmega169v/l 2514j?avr?12/03 port c input pins address ? pinc port d data register ? portd port d data direction register ? ddrd port d input pins address ? pind port e data register ? porte port e data direction register ? ddre port e input pins address ? pine port f data register ? portf port f data direction register ? ddrf bit 76543210 pinc7 pinc6 pinc5 pinc4 pinc3 pinc2 pinc1 pinc0 pinc read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value n/a n/a n/a n/a n/a n/a n/a n/a bit 76543210 portd7 portd6 portd5 portd4 portd3 portd2 portd1 portd0 portd read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 ddd7 ddd6 ddd5 ddd4 ddd3 ddd2 ddd1 ddd0 ddrd read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 pind7 pind6 pind5 pind4 pind3 pind2 pind1 pind0 pind read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value n/a n/a n/a n/a n/a n/a n/a n/a bit 76543210 porte7 porte6 porte5 porte4 porte3 porte2 porte1 porte0 porte read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 dde7 dde6 dde5 dde4 dde3 dde2 dde1 dde0 ddre read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 pine7 pine6 pine5 pine4 pine3 pine2 pine1 pine0 pine read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value n/a n/a n/a n/a n/a n/a n/a n/a bit 76543210 portf7 portf6 portf5 portf4 portf3 portf2 portf1 portf0 portf read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 ddf7 ddf6 ddf5 ddf4 ddf3 ddf2 ddf1 ddf0 ddrf read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 75 atmega169v/l 2514j?avr?12/03 port f input pins address ? pinf port g data register ? portg port g data direction register ? ddrg port g input pins address ? ping bit 76543210 pinf7 pinf6 pinf5 pinf4 pinf3 pinf2 pinf1 pinf0 pinf read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value n/a n/a n/a n/a n/a n/a n/a n/a bit 76543210 ??? portg4 portg3 portg2 portg1 portg0 portg read/write r r r r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 ? ? ? ddg4 ddg3 ddg2 ddg1 ddg0 ddrg read/write r r r r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 ? ? ? ping4 ping3 ping2 ping1 ping0 ping read/write r r r r/w r/w r/w r/w r/w initial value 0 0 0 n/a n/a n/a n/a n/a 76 atmega169v/l 2514j?avr?12/03 external interrupts the external interrupts are triggered by the int0 pin or any of the pcint15..0 pins. observe that, if enabled, the interrupts will trigger even if the int0 or pcint15..0 pins are configured as outputs. this feature provides a way of generating a software inter- rupt. the pin change interrupt pci1 will trigger if any enabled pcint15..8 pin toggles. pin change interrupts pci0 will trigger if any enabled pcint7..0 pin toggles. the pcmsk1 and pcmsk0 registers control which pins contribute to the pin change inter- rupts. pin change interrupts on pcint15..0 are detected asynchronously. this implies that these interrupts can be used for waking the part also from sleep modes other than idle mode. the int0 interrupts can be triggered by a falling or rising edge or a low level. this is set up as indicated in the specification for the external interrupt control register a ? eicra. when the int0 interrupt is enabled and is configured as level triggered, the interrupt will trigger as long as the pin is held low. note that recognition of falling or rising edge interrupts on int0 requires the presence of an i/o clock, described in ?clock sys- tems and their distribution? on page 23. low level interrupt on int0 is detected asynchronously. this implies that this interrupt can be used for waking the part also from sleep modes other than idle mode. the i/o clock is halted in all sleep modes except idle mode. note that if a level triggered interrupt is used for wake-up from power-down, the required level must be held long enough for the mcu to complete the wake-up to trigger the level interrupt. if the level disappears before the end of the start-up time, the mcu will still wake up, but no interrupt will be generated. the start-up time is defined by the sut and cksel fuses as described in ?system clock and clock options? on page 23. external interrupt control register a ? eicra the external interrupt control register a contains control bits for interrupt sense control. bit 1, 0 ? isc01, isc00: interrupt sense control 0 bit 1 and bit 0 the external interrupt 0 is activated by the external pin int0 if the sreg i-flag and the corresponding interrupt mask are set. the level and edges on the external int0 pin that activate the interrupt are defined in table 47. the value on the int0 pin is sampled before detecting edges. if edge or toggle interrupt is selected, pulses that last longer than one clock period will generate an interrupt. shorter pulses are not guaranteed to generate an interrupt. if low level interrupt is selected, the low level must be held until the completion of the currently executing instruction to generate an interrupt. bit 76543210 ? ? ? ? ? ? isc01 isc00 eicra read/write r r r r r r r/w r/w initial value00000000 table 47. interrupt 0 sense control isc01 isc00 description 0 0 the low level of int0 generates an interrupt request. 0 1 any logical change on int0 generates an interrupt request. 1 0 the falling edge of int0 generates an interrupt request. 1 1 the rising edge of int0 generates an interrupt request. 77 atmega169v/l 2514j?avr?12/03 external interrupt mask register ? eimsk bit 7 ? pcie1: pin change interrupt enable 1 when the pcie1 bit is set (one) and the i-bit in the status register (sreg) is set (one), pin change interrupt 1 is enabled. any change on any enabled pcint15..8 pin will cause an interrupt. the corresponding interrupt of pin change interrupt request is exe- cuted from the pci1 interrupt vector. pcint15..8 pins are enabled individually by the pcmsk1 register. bit 6 ? pcie0: pin change interrupt enable 0 when the pcie0 bit is set (one) and the i-bit in the status register (sreg) is set (one), pin change interrupt 0 is enabled. any change on any enabled pcint7..0 pin will cause an interrupt. the corresponding interrupt of pin change interrupt request is executed from the pci0 interrupt vector. pcint7..0 pins are enabled individually by the pcmsk0 register. bit 0 ? int0: external interrupt request 0 enable when the int0 bit is set (one) and the i-bit in the status register (sreg) is set (one), the external pin interrupt is enabled. the interrupt sense control0 bits 1/0 (isc01 and isc00) in the external interrupt control register a (eicra) define whether the external interrupt is activated on rising and/or falling edge of the int0 pin or level sensed. activity on the pin will cause an interrupt request even if int0 is configured as an output. the corresponding interrupt of external interrupt request 0 is executed from the int0 inter- rupt vector. external interrupt flag register ? eifr bit 7 ? pcif1: pin change interrupt flag 1 when a logic change on any pcint15..8 pin triggers an interrupt request, pcif1 becomes set (one). if the i-bit in sreg and the pcie1 bit in eimsk are set (one), the mcu will jump to the corresponding interrupt vector. the flag is cleared when the inter- rupt routine is executed. alternatively, the flag can be cleared by writing a logical one to it. bit 6 ? pcif0: pin change interrupt flag 0 when a logic change on any pcint7..0 pin triggers an interrupt request, pcif0 becomes set (one). if the i-bit in sreg and the pcie0 bit in eimsk are set (one), the mcu will jump to the corresponding interrupt vector. the flag is cleared when the inter- rupt routine is executed. alternatively, the flag can be cleared by writing a logical one to it. bit 76543210 pcie1 pcie0 ? ? ? ? ?int0eimsk read/writer/wr/wrrrrrr/w initial value00000000 bit 76543210 pcif1 pcif0 ? ? ? ? ? intf0 eifr read/writer/wr/wrrrrrr/w initial value00000000 78 atmega169v/l 2514j?avr?12/03 bit 0 ? intf0: external interrupt flag 0 when an edge or logic change on the int0 pin triggers an interrupt request, intf0 becomes set (one). if the i-bit in sreg and the int0 bit in eimsk are set (one), the mcu will jump to the corresponding interrupt vector. the flag is cleared when the inter- rupt routine is executed. alternatively, the flag can be cleared by writing a logical one to it. this flag is always cleared when int0 is configured as a level interrupt. pin change mask register 1 ? pcmsk1 bit 7..0 ? pcint15..8: pin change enable mask 15..8 each pcint15..8-bit selects whether pin change interrupt is enabled on the correspond- ing i/o pin. if pcint15..8 is set and the pcie1 bit in eimsk is set, pin change interrupt is enabled on the corresponding i/o pin. if pcint15..8 is cleared, pin change interrupt on the corresponding i/o pin is disabled. pin change mask register 0 ? pcmsk0 bit 7..0 ? pcint7..0: pin change enable mask 7..0 each pcint7..0 bit selects whether pin change interrupt is enabled on the correspond- ing i/o pin. if pcint7..0 is set and the pcie0 bit in eimsk is set, pin change interrupt is enabled on the corresponding i/o pin. if pcint7..0 is cleared, pin change interrupt on the corresponding i/o pin is disabled. bit 76543210 pcint15 pcint14 pcint13 pcint12 pcint11 pcint10 pcint9 pcint8 pcmsk1 read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 pcint7 pcint6 pcint5 pcint4 pcin t3 pcint2 pcint1 pcint0 pcmsk0 read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 79 atmega169v/l 2514j?avr?12/03 8-bit timer/counter0 with pwm timer/counter0 is a general purpose, single channel, 8-bit timer/counter module. the main features are: single channel counter clear timer on compare match (auto reload) glitch-free, phase correct pulse width modulator (pwm) frequency generator external event counter 10-bit clock prescaler overflow and compare match interrupt sources (tov0 and ocf0a) overview a simplified block diagram of the 8-bit timer/counter is shown in figure 26. for the actual placement of i/o pins, refer to ?pinout atmega169? on page 2. cpu accessible i/o registers, including i/o bits and i/o pins, are shown in bold. the device-specific i/o register and bit locations are listed in the ?8-bit timer/counter register description? on page 89. figure 26. 8-bit timer/counter block diagram registers the timer/counter (tcnt0) and output compare register (ocr0a) are 8-bit registers. interrupt request (abbreviated to int.req. in the figure) signals are all visible in the timer interrupt flag register (tifr0). all interrupts are individually masked with the timer interrupt mask register (timsk0). tifr0 and timsk0 are not shown in the figure. the timer/counter can be clocked internally, vi a the prescaler, or by an external clock source on the t0 pin. the clock select logic block controls which clock source and edge the timer/counter uses to increment (or decrement) its value. the timer/counter is inactive when no clock source is selected. the output from the clock select logic is referred to as the timer clock (clk t0 ). the double buffered output compare register (ocr0a) is compared with the timer/counter value at all times. the result of the compare can be used by the wave- form generator to generate a pwm or variable frequency output on the output compare pin (oc0a). see ?output compare unit? on page 81. for details. the compare match timer/counter data b u s = tcntn waveform generation ocn = 0 control logic = 0xff bottom count clear direction tovn (int.req.) ocrn tccrn clock select tn edge detector ( from prescaler ) clk tn top ocn (int.req.) 80 atmega169v/l 2514j?avr?12/03 event will also set the compare flag (ocf0a) which can be used to generate an output compare interrupt request. definitions many register and bit references in this section are written in general form. a lower case ?n? replaces the timer/counter number, in this case 0. a lower case ?x? replaces the output compare unit channel, in this case channel a. however, when using the register or bit defines in a program, the precise form must be used, i.e., tcnt0 for accessing timer/counter0 counter value and so on. the definitions in table 48 are also used extensively throughout the document. timer/counter clock sources the timer/counter can be clocked by an internal or an external clock source. the clock source is selected by the clock select logic which is controlled by the clock select (cs02:0) bits located in the timer/counter control register (tccr0a). for details on clock sources and prescaler, see ?timer/counter0 and timer/counter1 prescalers? on page 93. counter unit the main part of the 8-bit timer/counter is the programmable bi-directional counter unit. figure 27 shows a block diagram of the counter and its surroundings. figure 27. counter unit block diagram signal description (internal signals): count increment or decrement tcnt0 by 1. direction select between increment and decrement. clear clear tcnt0 (set all bits to zero). clk t n timer/counter clock, referred to as clk t0 in the following. top signalize that tcnt0 has reached maximum value. bottom signalize that tcnt0 has reached minimum value (zero). table 48. definitions bottom the counter reaches the bottom when it becomes 0x00. max the counter reaches its maximum when it becomes 0xff (decimal 255). top the counter reaches the top when it becomes equal to the highest value in the count sequence. the top value can be assigned to be the fixed value 0xff (max) or the value stored in the ocr0a register. the assignment is dependent on the mode of operation. data b u s tcntn control logic count tovn (int.req.) clock select top tn edge detector ( from prescaler ) clk tn bottom direction clear 81 atmega169v/l 2514j?avr?12/03 depending of the mode of operation used, the counter is cleared, incremented, or dec- remented at each timer clock (clk t0 ). clk t0 can be generated from an external or internal clock source, selected by the clock select bits (cs02:0). when no clock source is selected (cs02:0 = 0) the timer is stopped. however, the tcnt0 value can be accessed by the cpu, regardless of whether clk t0 is present or not. a cpu write overrides (has priority over) all counter clear or count operations. the counting sequence is determined by the setting of the wgm01 and wgm00 bits located in the timer/counter control register (tccr0a). there are close connections between how the counter behaves (counts) and how waveforms are generated on the output compare output oc0a. for more details about advanced counting sequences and waveform generation, see ?modes of operation? on page 84. the timer/counter overflow flag (tov0) is set according to the mode of operation selected by the wgm01:0 bits. tov0 can be used for generating a cpu interrupt. output compare unit the 8-bit comparator continuously compares tcnt0 with the output compare register (ocr0a). whenever tcnt0 equals ocr0a, the comparator signals a match. a match will set the output compare flag (ocf0a) at the next timer clock cycle. if enabled (ocie0a = 1 and global interrupt flag in sreg is set), the output compare flag gen- erates an output compare interrupt. the ocf0a flag is automatically cleared when the interrupt is executed. alternatively, the ocf0a flag can be cleared by software by writ- ing a logical one to its i/o bit location. the waveform generator uses the match signal to generate an output according to operating mode set by the wgm01:0 bits and com- pare output mode (com0a1:0) bits. the max and bottom signals are used by the waveform generator for handling the special cases of the extreme values in some modes of operation (see ?modes of operation? on page 84.). figure 28 shows a block diagram of the output compare unit. figure 28. output compare unit, block diagram ocfn x (int.req.) = (8-bit comparator ) ocrnx ocnx data b u s tcntn wgmn1:0 waveform generator top focn comnx1:0 bottom 82 atmega169v/l 2514j?avr?12/03 the ocr0a register is double buffered when using any of the pulse width modulation (pwm) modes. for the normal and clear ti mer on compare (ctc) modes of operation, the double buffering is disabled. the double buffering synchronizes the update of the ocr0 compare register to either top or bottom of the counting sequence. the synchro- nization prevents the occurrence of odd-length, non-symmetrical pwm pulses, thereby making the output glitch-free. the ocr0a register access may seem complex, but this is not case. when the double buffering is enabled, the cpu has access to the ocr0a buffer register, and if double buffering is disabled the cpu will access the ocr0a directly. force output compare in non-pwm waveform generation modes, the match output of the comparator can be forced by writing a one to the force output compare (foc0a) bit. forcing compare match will not set the ocf0a flag or reload/clear the timer, but the oc0a pin will be updated as if a real compare match had occurred (the com0a1:0 bits settings define whether the oc0a pin is set, cleared or toggled). compare match blocking by tcnt0 write all cpu write operations to the tcnt0 register will block any compare match that occur in the next timer clock cycle, even when the timer is stopped. this feature allows ocr0a to be initialized to the same value as tcnt0 without triggering an interrupt when the timer/counter clock is enabled. using the output compare unit since writing tcnt0 in any mode of operation will block all compare matches for one timer clock cycle, there are risks involved when changing tcnt0 when using the output compare channel, independently of whether the ti mer/counter is running or not. if the value written to tcnt0 equals the ocr0a value, the compare match will be missed, resulting in incorrect waveform generation. similarly, do not write the tcnt0 value equal to bottom when the counter is downcounting. the setup of the oc0a should be performed before setting the data direction register for the port pin to output. the easiest way of setting the oc0a value is to use the force output compare (foc0a) strobe bits in normal mode. the oc0a register keeps its value even when changing between waveform generation modes. be aware that the com0a1:0 bits are not double buffered together with the compare value. changing the com0a1:0 bits will take effect immediately. 83 atmega169v/l 2514j?avr?12/03 compare match output unit the compare output mode (com0a1:0) bits have two functions. the waveform gener- ator uses the com0a1:0 bits for defining the output compare (oc0a) state at the next compare match. also, the com0a1:0 bits control the oc0a pin output source. figure 29 shows a simplified schematic of the logic affected by the com0a1:0 bit setting. the i/o registers, i/o bits, and i/o pins in the figure are shown in bold. only the parts of the general i/o port control registers (ddr and port) that are affected by the com0a1:0 bits are shown. when referring to the oc0a state, the reference is for the internal oc0a register, not the oc0a pin. if a system rese t occur, the oc0a register is reset to ?0?. figure 29. compare match output unit, schematic the general i/o port function is overridden by the output compare (oc0a) from the waveform generator if either of the com0a1:0 bits are set. however, the oc0a pin direction (input or output) is still controlled by the data direction register (ddr) for the port pin. the data direction register bit for the oc0a pin (ddr_oc0a) must be set as output before the oc0a value is visible on the pin. the port override function is indepen- dent of the waveform generation mode. the design of the output compare pin logic allows initialization of the oc0a state before the output is enabled. note that some com0a1:0 bit settings are reserved for certain modes of operation. see ?8-bit timer/counter register description? on page 89. compare output mode and waveform generation the waveform generator uses the com0a1:0 bits differently in normal, ctc, and pwm modes. for all modes, setting the com0a1:0 = 0 tells the waveform generator that no action on the oc0a register is to be performed on the next compare match. for compare output actions in the non-pwm modes refer to table 50 on page 90. for fast pwm mode, refer to table 51 on page 90, and for phase correct pwm refer to table 52 on page 91. a change of the com0a1:0 bits state will have effect at the first compare match after the bits are written. for non-pwm modes, the action can be forced to have immediate effect by using the foc0a strobe bits. port ddr dq dq ocn pin ocnx dq waveform generator comnx1 comnx0 0 1 data b u s focn clk i/o 84 atmega169v/l 2514j?avr?12/03 modes of operation the mode of operation, i.e., the behavior of the timer/counter and the output compare pins, is defined by the combination of the waveform generation mode (wgm01:0) and compare output mode (com0a1:0) bits. the compare output mode bits do not affect the counting sequence, while the waveform generation mode bits do. the com0a1:0 bits control whether the pwm output generated should be inverted or not (inverted or non-inverted pwm). for non-pwm modes the com0a1:0 bits control whether the out- put should be set, cleared, or toggled at a compare match (see ?compare match output unit? on page 83.). for detailed timing information refer to figure 33, figure 34, figure 35 and figure 36 in ?timer/counter timing diagrams? on page 88. normal mode the simplest mode of operation is the normal mode (wgm01:0 = 0). in this mode the counting direction is always up (incrementing), and no counter clear is performed. the counter simply overruns when it passes its maximum 8-bit value (top = 0xff) and then restarts from the bottom (0x00). in normal operation the timer/counter overflow flag (tov0) will be set in the same timer clock cycle as the tcnt0 becomes zero. the tov0 flag in this case behaves like a ninth bit, except that it is only set, not cleared. however, combined with the timer overflow interrupt that automatically clears the tov0 flag, the timer resolution can be increased by software. there are no special cases to consider in the normal mode, a new counter value can be written anytime. the output compare unit can be used to generate interrupts at some given time. using the output compare to generate waveforms in normal mode is not recommended, since this will occupy too much of the cpu time. clear timer on compare match (ctc) mode in clear timer on compare or ctc mode (wgm01:0 = 2), the ocr0a register is used to manipulate the counter resolution. in ctc mode the counter is cleared to zero when the counter value (tcnt0) matches the ocr0a. the ocr0a defines the top value for the counter, hence also its resolution. this mode allows greater control of the compare match output frequency. it also simplifies the operation of counting external events. the timing diagram for the ctc mode is shown in figure 30. the counter value (tcnt0) increases until a compare match occurs between tcnt0 and ocr0a, and then counter (tcnt0) is cleared. figure 30. ctc mode, timing diagram an interrupt can be generated each time the counter value reaches the top value by using the ocf0a flag. if the interrupt is enabled, the interrupt handler routine can be used for updating the top value. however, changing top to a value close to bottom when the counter is running with none or a low prescaler value must be done with care since the ctc mode does not have the double buffering feature. if the new value written tcntn ocn (toggle) ocnx interrupt flag set 1 4 period 2 3 (comnx1:0 = 1) 85 atmega169v/l 2514j?avr?12/03 to ocr0a is lower than the current value of tcnt0, the counter will miss the compare match. the counter will then have to count to its maximum value (0xff) and wrap around starting at 0x00 before the compare match can occur. for generating a waveform output in ctc mode, the oc0a output can be set to toggle its logical level on each compare match by setting the compare output mode bits to tog- gle mode (com0a1:0 = 1). the oc0a value will not be visible on the port pin unless the data direction for the pin is set to output. the waveform generated will have a maximum frequency of f oc0 = f clk_i/o /2 when ocr0a is set to zero (0x00). the waveform frequency is defined by the following equation: the n variable represents the prescale factor (1, 8, 64, 256, or 1024). as for the normal mode of operation, the tov0 flag is set in the same timer clock cycle that the counter counts from max to 0x00. fast pwm mode the fast pulse width modulation or fast pwm mode (wgm01:0 = 3) provides a high fre- quency pwm waveform generation option. the fast pwm differs from the other pwm option by its single-slope operation. the counter counts from bottom to max then restarts from bottom. in non-inverting compare output mode, the output compare (oc0a) is cleared on the compare match between tcnt0 and ocr0a, and set at bot- tom. in inverting compare output mode, the output is set on compare match and cleared at bottom. due to the single-slope operation, the operating frequency of the fast pwm mode can be twice as high as the phase correct pwm mode that use dual- slope operation. this high frequency makes the fast pwm mode well suited for power regulation, rectification, and dac applications. high frequency allows physically small sized external components (coils, capacitors), and therefore reduces total system cost. in fast pwm mode, the counter is incremented until the counter value matches the max value. the counter is then cleared at the following timer clock cycle. the timing diagram for the fast pwm mode is shown in figure 31. the tcnt0 value is in the timing diagram shown as a histogram for illustrating the single-slope operation. the diagram includes non-inverted and inverted pwm outputs. the small horizontal line marks on the tcnt0 slopes represent compare matches between ocr0a and tcnt0. figure 31. fast pwm mode, timing diagram f ocnx f clk_i/o 2 n 1 ocrnx + () ?? ------------------------------------------------- - = tcntn ocrnx update and tovn interrupt flag set 1 period 2 3 ocn ocn (comnx1:0 = 2) (comnx1:0 = 3) ocrnx interrupt flag set 4 5 6 7 86 atmega169v/l 2514j?avr?12/03 the timer/counter overflow flag (tov0) is set each time the counter reaches max. if the interrupt is enabled, the interrupt handler routine can be used for updating the com- pare value. in fast pwm mode, the compare unit allows generation of pwm waveforms on the oc0a pin. setting the com0a1:0 bits to two will produce a non-inverted pwm and an inverted pwm output can be generated by setting the com0a1:0 to three (see table 51 on page 90). the actual oc0a value will only be visible on the port pin if the data direc- tion for the port pin is set as output. the pwm waveform is generated by setting (or clearing) the oc0a register at the compare match between ocr0a and tcnt0, and clearing (or setting) the oc0a register at the timer clock cycle the counter is cleared (changes from max to bottom). the pwm frequency for the output can be calculated by the following equation: the n variable represents the prescale factor (1, 8, 64, 256, or 1024). the extreme values for the ocr0a register represents special cases when generating a pwm waveform output in the fast pwm mode. if the ocr0a is set equal to bottom, the output will be a narrow spike for each max+1 timer clock cycle. setting the ocr0a equal to max will result in a constantly high or low output (depending on the polarity of the output set by the com0a1:0 bits.) a frequency (with 50% duty cycle) waveform output in fast pwm mode can be achieved by setting oc0a to toggle its logical level on each compare match (com0a1:0 = 1). the waveform generated will have a maximum frequency of f oc0 = f clk_i/o /2 when ocr0a is set to zero. this feature is similar to the oc0a toggle in ctc mode, except the double buffer feature of the output compare unit is enabled in the fast pwm mode. phase correct pwm mode the phase correct pwm mode (wgm01:0 = 1) provides a high resolution phase correct pwm waveform generation option. the phase correct pwm mode is based on a dual- slope operation. the counter counts repeatedly from bottom to max and then from max to bottom. in non-inverting compare output mode, the output compare (oc0a) is cleared on the compare match between tcnt0 and ocr0a while upcounting, and set on the compare match while downcounting. in inverting output compare mode, the operation is inverted. the dual-slope operation has lower maximum operation frequency than single slope operation. however, due to the symmetric feature of the dual-slope pwm modes, these modes are preferred for motor control applications. the pwm resolution for the phase correct pwm mode is fixed to eight bits. in phase correct pwm mode the counter is incremented until the counter value matches max. when the counter reaches max, it changes the count direction. the tcnt0 value will be equal to max for one timer clock cycle. the timing diagram for the phase correct pwm mode is shown on figure 32. the tcnt0 value is in the timing diagram shown as a histogram for illustrating the dual-slope operation. the diagram includes non-inverted and inverted pwm outputs. the small horizontal line marks on the tcnt0 slopes repre- sent compare matches between ocr0a and tcnt0. f ocnxpwm f clk_i/o n 256 ? ------------------ = 87 atmega169v/l 2514j?avr?12/03 figure 32. phase correct pwm mode, timing diagram the timer/counter overflow flag (tov0) is set each time the counter reaches bot- tom. the interrupt flag can be used to generate an interrupt each time the counter reaches the bottom value. in phase correct pwm mode, the compare unit allows generation of pwm waveforms on the oc0a pin. setting the com0a1:0 bits to two will produce a non-inverted pwm. an inverted pwm output can be generated by setting the com0a1:0 to three (see table 52 on page 91). the actual oc0a value will only be visible on the port pin if the data direc- tion for the port pin is set as output. the pwm waveform is generated by clearing (or setting) the oc0a register at the compare match between ocr0a and tcnt0 when the counter increments, and setting (or cleari ng) the oc0a register at compare match between ocr0a and tcnt0 when the counter decrements. the pwm frequency for the output when using phase correct pwm can be calculated by the following equation: the n variable represents the prescale factor (1, 8, 64, 256, or 1024). the extreme values for the ocr0a register represent special cases when generating a pwm waveform output in the phase correct pwm mode. if the ocr0a is set equal to bottom, the output will be continuously low and if set equal to max the output will be continuously high for non-inverted pwm mode. for inverted pwm the output will have the opposite logic values. at the very start of period 2 in figure 32 ocn has a transition from high to low even though there is no compare match. the point of this transition is to guarantee symmetry around bottom. there are two cases that give a transition without compare match. ocr0a changes its value from max, like in figure 32. when the ocr0a value is max the ocn pin value is the same as the result of a down-counting compare match. to ensure symmetry around bottom the ocn value at max must correspond to the result of an up-counting compare match. tovn interrupt flag set ocnx interrupt flag set 1 2 3 tcntn period ocn ocn (comnx1:0 = 2) (comnx1:0 = 3) ocrnx update f ocnxpcpwm f clk_i/o n 510 ? ------------------ = 88 atmega169v/l 2514j?avr?12/03 the timer starts counting from a value higher than the one in ocr0a, and for that reason misses the compare match and hence the ocn change that would have happened on the way up. timer/counter timing diagrams the timer/counter is a synchronous design and the timer clock (clk t0 ) is therefore shown as a clock enable signal in the following figures. the figures include information on when interrupt flags are set. figure 33 contains timing data for basic timer/counter operation. the figure shows the count sequence close to the max value in all modes other than phase correct pwm mode. figure 33. timer/counter timing diagram, no prescaling figure 34 shows the same timing data, but with the prescaler enabled. figure 34. timer/counter timing diagram, with prescaler (f clk_i/o /8) figure 35 shows the setting of ocf0a in all modes except ctc mode. figure 35. timer/counter timing diagram, setting of ocf0a, with prescaler (f clk_i/o /8) clk tn (clk i/o /1) tovn clk i/o tcntn max - 1 max bottom bottom + 1 tovn tcntn max - 1 max bottom bottom + 1 clk i/o clk tn (clk i/o /8) ocfnx ocrnx tcntn ocrnx value ocrnx - 1 ocrnx ocrnx + 1 ocrnx + 2 clk i/o clk tn (clk i/o /8) 89 atmega169v/l 2514j?avr?12/03 figure 36 shows the setting of ocf0a and the clearing of tcnt0 in ctc mode. figure 36. timer/counter timing diagram, clear timer on compare match mode, with prescaler (f clk_i/o /8) 8-bit timer/counter register description timer/counter control register a ? tccr0a bit 7 ? foc0a: force output compare a the foc0a bit is only active when the wgm00 bit specifies a non-pwm mode. how- ever, for ensuring compatibility with future devices, this bit must be set to zero when tccr0 is written when operating in pwm mode. when writing a logical one to the foc0a bit, an immediate compare match is forced on the waveform generation unit. the oc0a output is changed according to its com0a1:0 bits setting. note that the foc0a bit is implemented as a strobe. therefore it is the value present in the com0a1:0 bits that determines the effect of the forced compare. a foc0a strobe will not generate any interrupt, nor will it clear the timer in ctc mode using ocr0a as top. the foc0a bit is always read as zero. bit 6, 3 ? wgm01:0: waveform generation mode these bits control the counting sequence of the counter, the source for the maximum (top) counter value, and what type of waveform generation to be used. modes of oper- ation supported by the timer/counter unit are: normal mode, clear timer on compare match (ctc) mode, and two types of pulse width modulation (pwm) modes. see table 49 and ?modes of operation? on page 84. ocfnx ocrnx tcntn (ctc) top top - 1 top bottom bottom + 1 clk i/o clk tn (clk i/o /8) bit 76543210 foc0a wgm00 com0a1 com0a0 wgm01 cs02 cs01 cs00 tccr0 read/write w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 90 atmega169v/l 2514j?avr?12/03 note: 1. the ctc0 and pwm0 bit definition names are now obsolete. use the wgm01:0 def- initions. however, the functionality and location of these bits are compatible with previous versions of the timer. bit 5:4 ? com0a1:0: compare match output mode these bits control the output compare pin (oc0a) behavior. if one or both of the com0a1:0 bits are set, the oc0a output overrides the normal port functionality of the i/o pin it is connected to. however, note that the data direction register (ddr) bit cor- responding to the oc0a pin must be set in order to enable the output driver. when oc0a is connected to the pin, the function of the com0a1:0 bits depends on the wgm01:0 bit setting. table 50 shows the com0a1:0 bit functionality when the wgm01:0 bits are set to a normal or ctc mode (non-pwm). table 51 shows the com0a1:0 bit functionality when the wgm01:0 bits are set to fast pwm mode. note: 1. a special case occurs when ocr0a equals top and com0a1 is set. in this case, the compare match is ignored, but the set or clear is done at top. see ?fast pwm mode? on page 85 for more details. table 49. waveform generation mode bit description (1) mode wgm01 (ctc0) wgm00 (pwm0) timer/counter mode of operation top update of ocr0a at tov0 flag set on 0 0 0 normal 0xff immediate max 1 0 1 pwm, phase correct 0xff top bottom 2 1 0 ctc ocr0a immediate max 3 1 1 fast pwm 0xff top max table 50. compare output mode, non-pwm mode com0a1 com0a0 description 0 0 normal port operation, oc0a disconnected. 0 1 toggle oc0a on compare match 1 0 clear oc0a on compare match 1 1 set oc0a on compare match table 51. compare output mode, fast pwm mode (1) com0a1 com0a0 description 0 0 normal port operation, oc0a disconnected. 01reserved 1 0 clear oc0a on compare match, set oc0a at top 1 1 set oc0a on compare match, clear oc0a at top 91 atmega169v/l 2514j?avr?12/03 table 52 shows the com0a1:0 bit functionality when the wgm01:0 bits are set to phase correct pwm mode. note: 1. a special case occurs when ocr0a equals top and com0a1 is set. in this case, the compare match is ignored, but the set or clear is done at top. see ?phase cor- rect pwm mode? on page 86 for more details. bit 2:0 ? cs02:0: clock select the three clock select bits select the clock source to be used by the timer/counter. if external pin modes are used for the timer/counter0, transitions on the t0 pin will clock the counter even if the pin is configured as an output. this feature allows software control of the counting. timer/counter register ? tcnt0 the timer/counter register gives direct access, both for read and write operations, to the timer/counter unit 8-bit counter. writing to the tcnt0 register blocks (removes) the compare match on the following timer clock. modifying the counter (tcnt0) while the counter is running, introduces a risk of missing a compare match between tcnt0 and the ocr0a register. table 52. compare output mode, phase correct pwm mode (1) com0a1 com0a0 description 0 0 normal port operation, oc0a disconnected. 01reserved 1 0 clear oc0a on compare match when up-counting. set oc0a on compare match when downcounting. 1 1 set oc0a on compare match when up-counting. clear oc0a on compare match when downcounting. table 53. clock select bit description cs02 cs01 cs00 description 0 0 0 no clock source (timer/counter stopped) 001clk i/o /(no prescaling) 010clk i/o /8 (from prescaler) 011clk i/o /64 (from prescaler) 100clk i/o /256 (from prescaler) 101clk i/o /1024 (from prescaler) 1 1 0 external clock source on t0 pin. clock on falling edge. 1 1 1 external clock source on t0 pin. clock on rising edge. bit 76543210 tcnt0[7:0] tcnt0 read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 92 atmega169v/l 2514j?avr?12/03 output compare register a ? ocr0a the output compare register a contains an 8-bit value that is continuously compared with the counter value (tcnt0). a match can be used to generate an output compare interrupt, or to generate a waveform output on the oc0a pin. timer/counter 0 interrupt mask register ? timsk0 bit 1 ? ocie0a: timer/counter0 output compare match a interrupt enable when the ocie0a bit is written to one, and the i-bit in the status register is set (one), the timer/counter0 compare match a interrupt is enabled. the corresponding interrupt is executed if a compare match in timer/counter0 occurs, i.e., when the ocf0a bit is set in the timer/counter 0 interrupt flag register ? tifr0. bit 0 ? toie0: timer/counter0 overflow interrupt enable when the toie0 bit is written to one, and the i-bit in the status register is set (one), the timer/counter0 overflow interrupt is enabled. the corresponding interrupt is executed if an overflow in timer/counter0 occurs, i.e., when the tov0 bit is set in the timer/counter 0 interrupt flag register ? tifr0. timer/counter 0 interrupt flag register ? tifr0 bit 1 ? ocf0a: output compare flag 0 a the ocf0a bit is set (one) when a compare match occurs between the timer/counter0 and the data in ocr0a ? output compare register0. ocf0a is cleared by hardware when executing the corresponding interrupt handling vector. alternatively, ocf0a is cleared by writing a logic one to the flag. when the i-bit in sreg, ocie0a (timer/counter0 compare match interrupt enable), and ocf0a are set (one), the timer/counter0 compare match interrupt is executed. bit 0 ? tov0: timer/counter0 overflow flag the bit tov0 is set (one) when an overflow occurs in timer/counter0. tov0 is cleared by hardware when executing the corresponding interrupt handling vector. alternatively, tov0 is cleared by writing a logic one to the flag. when the sreg i-bit, toie0 (timer/counter0 overflow interrupt enable), and tov0 are set (one), the timer/counter0 overflow interrupt is executed. in phase correct pwm mode, this bit is set when timer/counter0 changes counting direction at 0x00. bit 76543210 ocr0a[7:0] ocr0 read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 ? ? ? ? ? ? ocie0a toie0 timsk0 read/write r r r r r r r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 ? ? ? ? ? ?ocf0a tov0 tifr0 read/write r r r r r r r/w r/w initial value00000000 93 atmega169v/l 2514j?avr?12/03 timer/counter0 and timer/counter1 prescalers timer/counter1 and timer/counter0 share the same prescaler module, but the timer/counters can have different prescaler settings. the description below applies to both timer/counter1 and timer/counter0. internal clock source the timer/counter can be clocked directly by the system clock (by setting the csn2:0 = 1). this provides the fastest operation, with a maximum timer/counter clock frequency equal to system clock frequency (f clk_i/o ). alternatively, one of four taps from the pres- caler can be used as a clock source. the prescaled clock has a frequency of either f clk_i/o /8, f clk_i/o /64, f clk_i/o /256, or f clk_i/o /1024. prescaler reset the prescaler is free running, i.e., operates independently of the clock select logic of the timer/counter, and it is shared by timer/counter1 and timer/counter0. since the prescaler is not affected by the timer/counter?s clock select, the state of the prescaler will have implications for situations where a prescaled clock is used. one example of prescaling artifacts occurs when the timer is enabled and clocked by the prescaler (6 > csn2:0 > 1). the number of system clock cycles from when the timer is enabled to the first count occurs can be from 1 to n+1 system clock cycles, where n equals the pres- caler divisor (8, 64, 256, or 1024). it is possible to use the prescaler reset for synchronizing the timer/counter to program execution. however, care must be taken if the other timer/counter that shares the same prescaler also uses prescaling. a prescaler reset will affect the prescaler period for all timer/counters it is connected to. external clock source an external clock source applied to the t1/t0 pin can be used as timer/counter clock (clk t1 /clk t0 ). the t1/t0 pin is sampled once every system clock cycle by the pin syn- chronization logic. the synchronized (sampled) signal is then passed through the edge detector. figure 37 shows a functional equivalent block diagram of the t1/t0 synchroni- zation and edge detector logic. the registers are clocked at the positive edge of the internal system clock ( clk i/o ). the latch is transparent in the high period of the internal system clock. the edge detector generates one clk t1 /clk t 0 pulse for each positive (csn2:0 = 7) or neg- ative (csn2:0 = 6) edge it detects. figure 37. t1/t0 pin sampling the synchronization and edge detector logic introduces a delay of 2.5 to 3.5 system clock cycles from an edge has been applied to the t1/t0 pin to the counter is updated. enabling and disabling of the clock input must be done when t1/t0 has been stable for at least one system clock cycle, otherwise it is a risk that a false timer/counter clock pulse is generated. each half period of the external clock applied must be longer than one system clock cycle to ensure correct sampling. the exter nal clock must be guaranteed to have less than half the system clock frequency (f extclk < f clk_i/o /2) given a 50/50% duty cycle. since tn_sync (to clock select logic) edge detector synchronization dq dq le dq tn clk i/o 94 atmega169v/l 2514j?avr?12/03 the edge detector uses sampling, the maximum frequency of an external clock it can detect is half the sampling frequency (nyquist sampling theorem). however, due to vari- ation of the system clock frequency and duty cycle caused by oscillator source (crystal, resonator, and capacitors) tolerances, it is recommended that maximum frequency of an external clock source is less than f clk_i/o /2.5. an external clock source can not be prescaled. figure 38. prescaler for timer/counter0 and timer/counter1 (1) note: 1. the synchronization logic on the input pins ( t1/t0) is shown in figure 37. general timer/counter control register ? gtccr bit 7 ? tsm: timer/counter synchronization mode writing the tsm bit to one activates the timer/counter synchronization mode. in this mode, the value that is written to the psr2 and psr10 bits is kept, hence keeping the corresponding prescaler reset signals asserted. this ensures that the corresponding timer/counters are halted and can be configured to the same value without the risk of one of them advancing during configuration. when the tsm bit is written to zero, the psr2 and psr10 bits are cleared by hardware, and the timer/counters start counting simultaneously. bit 0 ? psr10: prescaler reset timer/counter1 and timer/counter0 when this bit is one, timer/counter1 and timer/counter0 prescaler will be reset. this bit is normally cleared immediately by hardware, except if the tsm bit is set. note that timer/counter1 and timer/counter0 share the same prescaler and a reset of this pres- caler will affect both timers. psr10 clear clk t1 clk t0 t1 t0 clk i/o synchronization synchronization bit 7 6 5 4 3 2 1 0 tsm ? ? ? ? ? psr2 psr10 gtccr read/write r/w r r r r r r/w r/w initial value 0 0 0 0 0 0 0 0 95 atmega169v/l 2514j?avr?12/03 16-bit timer/counter1 the 16-bit timer/counter unit allows accurate program execution timing (event man- agement), wave generation, and signal timing measurement. the main features are: true 16-bit design (i.e., allows 16-bit pwm) two independent output compare units double buffered output compare registers one input capture unit input capture noise canceler clear timer on compare match (auto reload) glitch-free, phase correct pulse width modulator (pwm) variable pwm period frequency generator external event counter four independent interrupt sources (tov1, ocf1a, ocf1b, and icf1) overview most register and bit references in this section are written in general form. a lower case ?n? replaces the timer/counter number, and a lower case ?x? replaces the output com- pare unit channel. however, when using the register or bit defines in a program, the precise form must be used, i.e., tcnt1 for accessing timer/counter1 counter value and so on. a simplified block diagram of the 16-bit timer/counter is shown in figure 39. for the actual placement of i/o pins, refer to ?pinout atmega169? on page 2. cpu accessible i/o registers, including i/o bits and i/o pins, are shown in bold. the device-specific i/o register and bit locations are listed in the ?16-bit timer/counter register description? on page 117. 96 atmega169v/l 2514j?avr?12/03 figure 39. 16-bit timer/counter block diagram (1) note: 1. refer to figure 1 on page 2, table 28 on page 60, and table 34 on page 64 for timer/counter1 pin placement and description. registers the timer/counter (tcnt1), output compare registers (ocr1a/b), and input capture register (icr1) are all 16-bit registers. special procedures must be followed when accessing the 16-bit registers. these procedures are described in the section ?access- ing 16-bit registers? on page 98. the timer/counter control registers (tccr1a/b) are 8-bit registers and have no cpu access restri ctions. interrupt requests (abbreviated to int.req. in the figure) signals are all visible in the timer interrupt flag register (tifr1). all interrupts are individually masked with the timer interrupt mask register (timsk1). tifr1 and timsk1 are not shown in the figure. the timer/counter can be clocked internally, vi a the prescaler, or by an external clock source on the t1 pin. the clock select logic block controls which clock source and edge the timer/counter uses to increment (or decrement) its value. the timer/counter is inactive when no clock source is selected. the output from the clock select logic is referred to as the timer clock (clk t 1 ). the double buffered output compare registers (ocr1a/b) are compared with the timer/counter value at all time. the result of the compare can be used by the waveform generator to generate a pwm or variable frequency output on the output compare pin (oc1a/b). see ?output compare units? on page 104.. the compare match event will clock select timer/counter data b u s ocrna ocrnb icrn = = tcntn waveform generation waveform generation ocna ocnb noise canceler icpn = fixed top values edge detector control logic = 0 top bottom count clear direction tovn (int.req.) ocna (int.req.) ocnb (int.req.) icfn (int.req.) tccrna tccrnb ( from analog comparator ouput ) tn edge detector ( from prescaler ) clk tn 97 atmega169v/l 2514j?avr?12/03 also set the compare match flag (ocf1a/b) which can be used to generate an output compare interrupt request. the input capture register can capture the timer/counter value at a given external (edge triggered) event on either the input capture pin (icp1) or on the analog compar- ator pins (see ?analog comparator? on page 189.) the input capture unit includes a digital filtering unit (noise canceler) for reducing the chance of capturing noise spikes. the top value, or maximum timer/counter value, can in some modes of operation be defined by either the ocr1a register, the icr1 register, or by a set of fixed values. when using ocr1a as top value in a pwm mode, the ocr1a register can not be used for generating a pwm output. however, the top value will in this case be double buffered allowing the top value to be changed in run time. if a fixed top value is required, the icr1 register can be used as an alternative, freeing the ocr1a to be used as pwm output. definitions the following definitions are used extensively throughout the section: compatibility the 16-bit timer/counter has been updated and improved from previous versions of the 16-bit avr timer/counter. this 16-bit timer/counter is fully compatible with the earlier version regarding: all 16-bit timer/counter related i/o register address locations, including timer interrupt registers. bit locations inside all 16-bit timer/counter registers, including timer interrupt registers. interrupt vectors. the following control bits have changed name, but have same functionality and register location: pwm10 is changed to wgm10. pwm11 is changed to wgm11. ctc1 is changed to wgm12. the following bits are added to the 16-bit timer/counter control registers: foc1a and foc1b are added to tccr1c. wgm13 is added to tccr1b. the 16-bit timer/counter has improvements that will affect the compatibility in some special cases. table 54. definitions bottom the counter reaches the bottom when it becomes 0x0000. max the counter reaches its max imum when it becomes 0xffff (decimal 65535). top the counter reaches the top when it becomes equal to the highest value in the count sequence. the top value can be assigned to be one of the fixed values: 0x00ff, 0x01ff, or 0x03ff, or to the va lue stored in the ocr1a or icr1 regis- ter. the assignment is dependent of the mode of operation. 98 atmega169v/l 2514j?avr?12/03 accessing 16-bit registers the tcnt1, ocr1a/b, and icr1 are 16-bit registers that can be accessed by the avr cpu via the 8-bit data bus. the 16-bit register must be byte accessed using two read or write operations. each 16-bit timer has a single 8-bit register for temporary storing of the high byte of the 16-bit access. the same temporary register is shared between all 16-bit registers within each 16-bit timer. accessing the low byte triggers the 16-bit read or write operation. when the low byte of a 16-bit register is written by the cpu, the high byte stored in the temporary register, and the low byte written are both copied into the 16-bit register in the same clock cycle. when the low byte of a 16-bit register is read by the cpu, the high byte of the 16-bit register is copied into the temporary register in the same clock cycle as the low byte is read. not all 16-bit accesses uses the temporary register for the high byte. reading the ocr1a/b 16-bit registers does not involve using the temporary register. to do a 16-bit write, the high byte must be written before the low byte. for a 16-bit read, the low byte must be read before the high byte. the following code examples show how to access the 16-bit timer registers assuming that no interrupts updates the temporary register. the same principle can be used directly for accessing the ocr1a/b and icr1 registers. note that when using ?c?, the compiler handles the 16-bit access. note: 1. the example code assumes that the part specific header file is included. for i/o registers located in extended i/o ma p, ?in?, ?out?, ?sbis?, ?sbic?, ?cbi?, and ?sbi? instructions must be replaced with instructions that allow access to extended i/o. typically ?lds? and ?sts? combined with ?sbrs?, ?sbrc?, ?sbr?, and ?cbr?. the assembly code example returns the tcnt1 value in the r17:r16 register pair. it is important to notice that accessing 16-bit registers are atomic operations. if an inter- rupt occurs between the two instructions accessing the 16-bit register, and the interrupt code updates the temporary register by accessing the same or any other of the 16-bit timer registers, then the result of the access outside the interrupt will be corrupted. assembly code examples (1) ... ; set tcnt 1 to 0x01ff ldi r17,0x01 ldi r16,0xff out tcnt 1 h,r17 out tcnt 1 l,r16 ; read tcnt 1 into r17:r16 in r16,tcnt 1 l in r17,tcnt 1 h ... c code examples (1) unsigned int i; ... /* set tcnt 1 to 0x01ff */ tcnt 1 = 0x1ff; /* read tcnt 1 into i */ i = tcnt 1 ; ... 99 atmega169v/l 2514j?avr?12/03 therefore, when both the main code and the interrupt code update the temporary regis- ter, the main code must disable the interrupts during the 16-bit access. the following code examples show how to do an atomic read of the tcnt1 register contents. reading any of the ocr1a/b or icr1 registers can be done by using the same principle. note: 1. the example code assumes that the part specific header file is included. for i/o registers located in extended i/o ma p, ?in?, ?out?, ?sbis?, ?sbic?, ?cbi?, and ?sbi? instructions must be replaced with instructions that allow access to extended i/o. typically ?lds? and ?sts? combined with ?sbrs?, ?sbrc?, ?sbr?, and ?cbr?. the assembly code example returns the tcnt1 value in the r17:r16 register pair. assembly code example (1) tim16_readtcnt 1 : ; save global interrupt flag in r18,sreg ; disable interrupts cli ; read tcnt 1 into r17:r16 in r16,tcnt 1 l in r17,tcnt 1 h ; restore global interrupt flag out sreg,r18 ret c code example (1) unsigned int tim16_readtcnt 1 ( void ) { unsigned char sreg; unsigned int i; /* save global interrupt flag */ sreg = sreg; /* disable interrupts */ _cli(); /* read tcnt 1 into i */ i = tcnt 1 ; /* restore global interrupt flag */ sreg = sreg; return i; } 100 atmega169v/l 2514j?avr?12/03 the following code examples show how to do an atomic write of the tcnt1 register contents. writing any of the ocr1a/b or icr1 registers can be done by using the same principle. note: 1. the example code assumes that the part specific header file is included. for i/o registers located in extended i/o ma p, ?in?, ?out?, ?sbis?, ?sbic?, ?cbi?, and ?sbi? instructions must be replaced with instructions that allow access to extended i/o. typically ?lds? and ?sts? combined with ?sbrs?, ?sbrc?, ?sbr?, and ?cbr?. the assembly code example requires that the r17:r16 register pair contains the value to be written to tcnt1. reusing the temporary high byte register if writing to more than one 16-bit register where the high byte is the same for all registers written, then the high byte only needs to be written once. however, note that the same rule of atomic operation described previously also applies in this case. assembly code example (1) tim16_writetcnt 1 : ; save global interrupt flag in r18,sreg ; disable interrupts cli ; set tcnt 1 to r17:r16 out tcnt 1 h,r17 out tcnt 1 l,r16 ; restore global interrupt flag out sreg,r18 ret c code example (1) void tim16_writetcnt 1 ( unsigned int i ) { unsigned char sreg; unsigned int i; /* save global interrupt flag */ sreg = sreg; /* disable interrupts */ _cli(); /* set tcnt 1 to i */ tcnt 1 = i; /* restore global interrupt flag */ sreg = sreg; } 101 atmega169v/l 2514j?avr?12/03 timer/counter clock sources the timer/counter can be clocked by an internal or an external clock source. the clock source is selected by the clock select logic which is controlled by the clock select (cs12:0) bits located in the timer/counter control register b (tccr1b). for details on clock sources and prescaler, see ?timer/counter0 and timer/counter1 prescalers? on page 93. counter unit the main part of the 16-bit timer/counter is the programmable 16-bit bi-directional counter unit. figure 40 shows a block diagram of the counter and its surroundings. figure 40. counter unit block diagram signal description (internal signals): count increment or decrement tcnt1 by 1. direction select between increment and decrement. clear clear tcnt1 (set all bits to zero). clk t 1 timer/counter clock. top signalize that tcnt1 has reached maximum value. bottom signalize that tcnt1 has reached minimum value (zero). the 16-bit counter is mapped into two 8-bit i/o memory locations: counter high (tcnt1h) containing the upper eight bits of the counter, and counter low (tcnt1l) containing the lower eight bits. the tcnt1h register can only be indirectly accessed by the cpu. when the cpu does an access to the tcnt1h i/o location, the cpu accesses the high byte temporary register (temp). the temporary register is updated with the tcnt1h value when the tcnt1l is read, and tcnt1h is updated with the temporary register value when tcnt1l is writt en. this allows the cpu to read or write the entire 16-bit counter value within one cl ock cycle via the 8-bit data bus. it is impor- tant to notice that there are special cases of writing to the tcnt1 register when the counter is counting that will give unpredictable results. the special cases are described in the sections where they are of importance. depending on the mode of operation used, the counter is cleared, incremented, or dec- remented at each timer clock (clk t 1 ). the clk t 1 can be generated from an external or internal clock source, selected by the clock select bits (cs12:0). when no clock source is selected (cs12:0 = 0) the timer is stopped. however, the tcnt1 value can be accessed by the cpu, independent of whether clk t 1 is present or not. a cpu write over- rides (has priority over) all counter clear or count operations. the counting sequence is determined by the setting of the waveform generation mode bits (wgm13:0) located in the timer/counter control registers a and b (tccr1a and tccr1b). there are close connections between how the counter behaves (counts) and temp (8-bit) data b u s (8-bit) tcntn (16-bit counter) tcntnh (8-bit) tcntnl (8-bit) control logic count clear direction tovn (int.req.) clock select top bottom tn edge detector ( from prescaler ) clk tn 102 atmega169v/l 2514j?avr?12/03 how waveforms are generated on the output compare outputs oc1x. for more details about advanced counting sequences and waveform generation, see ?modes of opera- tion? on page 107. the timer/counter overflow flag (tov1) is set according to the mode of operation selected by the wgm13:0 bits. tov1 can be used for generating a cpu interrupt. input capture unit the timer/counter incorporates an input capture unit that can capture external events and give them a time-stamp indicating time of occurrence. the external signal indicating an event, or multiple events, can be applied via the icp1 pin or alternatively, via the analog-comparator unit. the time-stamps can then be used to calculate frequency, duty- cycle, and other features of the signal applied. alternatively the time-stamps can be used for creating a log of the events. the input capture unit is illustrated by the block diagram shown in figure 41. the ele- ments of the block diagram that are not directly a part of the input capture unit are gray shaded. the small ?n? in register and bit names indicates the timer/counter number. figure 41. input capture unit block diagram when a change of the logic level (an event) occurs on the input capture pin (icp1), alternatively on the analog comparator output (aco), and this change confirms to the setting of the edge detector, a capture will be triggered. when a capture is triggered, the 16-bit value of the counter (tcnt1) is written to the input capture register (icr1). the input capture flag (icf1) is set at the same system clock as the tcnt1 value is copied into icr1 register. if enabled (icie1 = 1), the input capture flag generates an input capture interrupt. the icf1 flag is automatically cleared when the interrupt is executed. alternatively the icf1 flag can be cleared by software by writing a logical one to its i/o bit location. reading the 16-bit value in the input capture register (icr1) is done by first reading the low byte (icr1l) and then the high byte (icr1h). when the low byte is read the high byte is copied into the high byte temporary register (temp). when the cpu reads the icr1h i/o location it will access the temp register. icfn (int.req.) analog comparator write icrn (16-bit register) icrnh (8-bit) noise canceler icpn edge detector temp (8-bit) data bus (8-bit) icrnl (8-bit) tcntn (16-bit counter) tcntnh (8-bit) tcntnl (8-bit) acic* icnc ices aco* 103 atmega169v/l 2514j?avr?12/03 the icr1 register can only be written when using a waveform generation mode that utilizes the icr1 register for defining the counter?s top value. in these cases the waveform generation mode (wgm13:0) bits must be set before the top value can be written to the icr1 register. when writing the icr1 register the high byte must be writ- ten to the icr1h i/o location before the low byte is written to icr1l. for more information on how to access the 16-bit registers refer to ?accessing 16-bit registers? on page 98. input capture trigger source the main trigger source for the input capture unit is the input capture pin (icp1). timer/counter1 can alternatively use the analog comparator output as trigger source for the input capture unit. the analog comparator is selected as trigger source by set- ting the analog comparator input capture (acic) bit in the analog comparator control and status register (acsr). be aware that changing tr igger source can trigger a cap- ture. the input capture flag must therefore be cleared after the change. both the input capture pin (icp1) and the analog comparator output (aco) inputs are sampled using the same technique as for the t1 pin (figure 37 on page 93). the edge detector is also identical. however, when the noise canceler is enabled, additional logic is inserted before the edge detector, which increases the delay by four system clock cycles. note that the input of the noise canceler and edge detector is always enabled unless the timer/counter is set in a waveform generation mode that uses icr1 to define top. an input capture can be triggered by software by controlling the port of the icp1 pin. noise canceler the noise canceler improves noise immunity by using a simple digital filtering scheme. the noise canceler input is monitored over four samples, and all four must be equal for changing the output that in turn is used by the edge detector. the noise canceler is enabled by setting the input capture noise canceler (icnc1) bit in timer/counter control register b (tccr1b). when enabled the noise canceler intro- duces additional four system clock cycles of delay from a change applied to the input, to the update of the icr1 register. the noise canceler uses the system clock and is there- fore not affected by the prescaler. using the input capture unit the main challenge when using the input capture unit is to assign enough processor capacity for handling the incoming events. the time between two events is critical. if the processor has not read the captured value in the icr1 register before the next event occurs, the icr1 will be overwritten with a new value. in this case the result of the cap- ture will be incorrect. when using the input capture interrupt, the icr1 register should be read as early in the interrupt handler routine as possible. even though the input capture interrupt has rela- tively high priority, the maximum interrupt response time is dependent on the maximum number of clock cycles it takes to handle any of the other interrupt requests. using the input capture unit in any mode of operation when the top value (resolution) is actively changed during operation, is not recommended. measurement of an external signal?s duty cycle requires that the trigger edge is changed after each capture. changing the edge sensing must be done as early as possible after the icr1 register has been read. after a change of the edge, the input capture flag (icf1) must be cleared by software (writing a logical one to the i/o bit location). for measuring frequency only, the clearing of the icf1 flag is not required (if an interrupt handler is used). 104 atmega169v/l 2514j?avr?12/03 output compare units the 16-bit comparator continuously compares tcnt1 with the output compare regis- ter (ocr1x). if tcnt equals ocr1x the comparator signals a match. a match will set the output compare flag (ocf1x) at the next timer clock cycle . if enabled (ocie1x = 1), the output compare flag generates an output compare interrupt. the ocf1x flag is automatically cleared when the interrupt is executed. alternatively the ocf1x flag can be cleared by software by writing a logical one to its i/o bit location. the waveform generator uses the match signal to generate an output according to operating mode set by the waveform generation mode (wgm13:0) bits and compare output mode (com1x1:0) bits. the top and bottom signals are used by the waveform generator for handling the special cases of the extreme values in some modes of operation (see ?modes of operation? on page 107.) a special feature of output compare unit a allows it to define the timer/counter top value (i.e., counter resolution). in addition to the counter resolution, the top value defines the period time for waveforms generated by the waveform generator. figure 42 shows a block diagram of the output compare unit. the small ?n? in the regis- ter and bit names indicates the device number (n = 1 for timer/counter 1), and the ?x? indicates output compare unit (a/b). the elements of the block diagram that are not directly a part of the output compare unit are gray shaded. figure 42. output compare unit, block diagram the ocr1x register is double buffered when using any of the twelve pulse width mod- ulation (pwm) modes. for the normal and clear timer on compare (ctc) modes of operation, the double buffering is disabled. the double buffering synchronizes the update of the ocr1x compare register to either top or bottom of the counting sequence. the synchronization prevents the occurrence of odd-length, non-symmetrical pwm pulses, thereby making the output glitch-free. the ocr1x register access may seem complex, but this is not case. when the double buffering is enabled, the cpu has access to the ocr1x buffer register, and if double buffering is disabled the cpu will access the ocr1x directly. the content of the ocr1x ocfnx (int.req.) = (16-bit comparator ) ocrnx buffer (16-bit register) ocrnxh buf. (8-bit) ocnx temp (8-bit) data bus (8-bit) ocrnxl buf. (8-bit) tcntn (16-bit counter) tcntnh (8-bit) tcntnl (8-bit) comnx1:0 wgmn3:0 ocrnx (16-bit register) ocrnxh (8-bit) ocrnxl (8-bit) waveform generator top bottom 105 atmega169v/l 2514j?avr?12/03 (buffer or compare) register is only changed by a write operation (the timer/counter does not update this register automatically as the tcnt1 and icr1 register). therefore ocr1x is not read via the high byte temporary register (temp). however, it is a good practice to read the low byte first as when accessing other 16-bit registers. writing the ocr1x registers must be done via the temp register since the compare of all 16 bits is done continuously. the high byte (ocr1xh) has to be written first. when the high byte i/o location is written by the cpu, the temp register will be updated by the value written. then when the low byte (ocr1xl) is written to the lower eight bits, the high byte will be copied into the upper 8-bits of either the ocr1x buffer or ocr1x compare reg- ister in the same system clock cycle. for more information of how to access the 16-bit registers refer to ?accessing 16-bit registers? on page 98. force output compare in non-pwm waveform generation modes, the match output of the comparator can be forced by writing a one to the force output compare (foc1x) bit. forcing compare match will not set the ocf1x flag or reload/clear the timer, but the oc1x pin will be updated as if a real compare match had occurred (the comx1:0 bits settings define whether the oc1x pin is set, cleared or toggled). compare match blocking by tcnt1 write all cpu writes to the tcnt1 register will block any compare match that occurs in the next timer clock cycle, even when the timer is stopped. this feature allows ocr1x to be initialized to the same value as tcnt1 without triggering an interrupt when the timer/counter clock is enabled. using the output compare unit since writing tcnt1 in any mode of operation will block all compare matches for one timer clock cycle, there are risks involved when changing tcnt1 when using any of the output compare channels, independent of whether the timer/counter is running or not. if the value written to tcnt1 equals the ocr1x value, the compare match will be missed, resulting in incorrect waveform generation. do not write the tcnt1 equal to top in pwm modes with variable top values. the compare match for the top will be ignored and the counter will continue to 0xffff. similarly, do not write the tcnt1 value equal to bottom when the counter is downcounting. the setup of the oc1x should be performed before setting the data direction register for the port pin to output. the easiest way of setting the oc1x value is to use the force output compare (foc1x) strobe bits in normal mode. the oc1x register keeps its value even when changing between waveform generation modes. be aware that the com1x1:0 bits are not double buffered together with the compare value. changing the com1x1:0 bits will take effect immediately. 106 atmega169v/l 2514j?avr?12/03 compare match output unit the compare output mode (com1x1:0) bits have two functions. the waveform gener- ator uses the com1x1:0 bits for defining the output compare (oc1x) state at the next compare match. secondly the com1x1:0 bits control the oc1x pin output source. fig- ure 43 shows a simplified schematic of the logic affected by the com1x1:0 bit setting. the i/o registers, i/o bits, and i/o pins in the figure are shown in bold. only the parts of the general i/o port control registers (ddr and port) that are affected by the com1x1:0 bits are shown. when referring to the oc1x state, the reference is for the internal oc1x register, not the oc1x pin. if a system reset occur, the oc1x register is reset to ?0?. figure 43. compare match output unit, schematic the general i/o port function is overridden by the output compare (oc1x) from the waveform generator if either of the com1x1:0 bits are set. however, the oc1x pin direction (input or output) is still controlled by the data direction register (ddr) for the port pin. the data direction register bit for the oc1x pin (ddr_oc1x) must be set as output before the oc1x value is visible on the pin. the port override function is generally independent of the waveform generation mode, but there are some exceptions. refer to table 55, table 56 and table 57 for details. the design of the output compare pin logic allows initialization of the oc1x state before the output is enabled. note that some com1x1:0 bit settings are reserved for certain modes of operation. see ?16-bit timer/counter register description? on page 117. the com1x1:0 bits have no effect on the input capture unit. port ddr dq dq ocnx pin ocnx dq waveform generator comnx1 comnx0 0 1 data b u s focnx clk i/o 107 atmega169v/l 2514j?avr?12/03 compare output mode and waveform generation the waveform generator uses the com1x1:0 bits differently in normal, ctc, and pwm modes. for all modes, setting the com1x1:0 = 0 tells the waveform generator that no action on the oc1x register is to be performed on the next compare match. for com- pare output actions in the non-pwm modes refer to table 55 on page 117. for fast pwm mode refer to table 56 on page 117, and for phase correct and phase and fre- quency correct pwm refer to table 57 on page 118. a change of the com1x1:0 bits state will have effect at the first compare match after the bits are written. for non-pwm modes, the action can be forced to have immediate effect by using the foc1x strobe bits. modes of operation the mode of operation, i.e., the behavior of the timer/counter and the output compare pins, is defined by the combination of the waveform generation mode (wgm13:0) and compare output mode (com1x1:0) bits. the compare output mode bits do not affect the counting sequence, while the waveform generation mode bits do. the com1x1:0 bits control whether the pwm output generated should be inverted or not (inverted or non-inverted pwm). for non-pwm modes the com1x1:0 bits control whether the out- put should be set, cleared or toggle at a compare match (see ?compare match output unit? on page 106.) for detailed timing information refer to ?timer/counter timing diagrams? on page 115. normal mode the simplest mode of operation is the normal mode (wgm13:0 = 0). in this mode the counting direction is always up (incrementing), and no counter clear is performed. the counter simply overruns when it passes its maximum 16-bit value (max = 0xffff) and then restarts from the bottom (0x0000). in normal operation the timer/counter over- flow flag (tov1) will be set in the same timer clock cycle as the tcnt1 becomes zero. the tov1 flag in this case behaves like a 17th bit, except that it is only set, not cleared. however, combined with the timer overflow interrupt that automatically clears the tov1 flag, the timer resolution can be increased by software. there are no special cases to consider in the normal mode, a new counter value can be written anytime. the input capture unit is easy to use in normal mode. however, observe that the maxi- mum interval between the external events must not exceed the resolution of the counter. if the interval between events are too long, the timer overflow interrupt or the prescaler must be used to extend the resolution for the capture unit. the output compare units can be used to generate interrupts at some given time. using the output compare to generate waveforms in normal mode is not recommended, since this will occupy too much of the cpu time. 108 atmega169v/l 2514j?avr?12/03 clear timer on compare match (ctc) mode in clear timer on compare or ctc mode (wgm13:0 = 4 or 12), the ocr1a or icr1 register are used to manipulate the counter resolution. in ctc mode the counter is cleared to zero when the counter value (tcnt1) matches either the ocr1a (wgm13:0 = 4) or the icr1 (wgm13:0 = 12). the ocr1a or icr1 define the top value for the counter, hence also its resolution. this m ode allows greater control of the compare match output frequency. it also simplifies the operation of counting external events. the timing diagram for the ctc mode is shown in figure 44. the counter value (tcnt1) increases until a compare match occurs with either ocr1a or icr1, and then counter (tcnt1) is cleared. figure 44. ctc mode, timing diagram an interrupt can be generated at each time the counter value reaches the top value by either using the ocf1a or icf1 flag according to the register used to define the top value. if the interrupt is enabled, the interrupt handler routine can be used for updating the top value. however, changing the top to a value close to bottom when the counter is running with none or a low prescaler value must be done with care since the ctc mode does not have the double buffering feature. if the new value written to ocr1a or icr1 is lower than the current value of tcnt1, the counter will miss the com- pare match. the counter will then have to count to its maximum value (0xffff) and wrap around starting at 0x0000 before the compare match can occur. in many cases this feature is not desirable. an alternative will then be to use the fast pwm mode using ocr1a for defining top (wgm13:0 = 15) since the ocr1a then will be double buffered. for generating a waveform output in ctc mode, the oc1a output can be set to toggle its logical level on each compare match by setting the compare output mode bits to tog- gle mode (com1a1:0 = 1). the oc1a value will not be visible on the port pin unless the data direction for the pin is set to output (ddr_oc1a = 1). the waveform generated will have a maximum frequency of f oc 1 a = f clk_i/o /2 when ocr1a is set to zero (0x0000). the waveform frequency is defined by the following equation: the n variable represents the prescaler factor (1, 8, 64, 256, or 1024). as for the normal mode of operation, the tov1 flag is set in the same timer clock cycle that the counter counts from max to 0x0000. tcntn ocna (toggle) ocna interrupt flag set or icfn interrupt flag set (interrupt on top) 1 4 period 2 3 (comna1:0 = 1) f ocna f clk_i/o 2 n 1 ocrna + () ?? -------------------------------------------------- - = 109 atmega169v/l 2514j?avr?12/03 fast pwm mode the fast pulse width modulation or fast pwm mode (wgm13:0 = 5, 6, 7, 14, or 15) pro- vides a high frequency pwm waveform generation option. the fast pwm differs from the other pwm options by its single-slope operation. the counter counts from bottom to top then restarts from bottom. in non-inverting compare output mode, the output compare (oc1x) is set on the compare match between tcnt1 and ocr1x, and cleared at top. in inverting compare output mode output is cleared on compare match and set at top. due to the single-slope operation, the operating frequency of the fast pwm mode can be twice as high as the phase correct and phase and frequency correct pwm modes that use dual-slope operation. this high frequency makes the fast pwm mode well suited for power regulation, rectification, and dac applications. high fre- quency allows physically small sized external components (coils, capacitors), hence reduces total system cost. the pwm resolution for fast pwm can be fixed to 8-, 9-, or 10-bit, or defined by either icr1 or ocr1a. the minimum resolution allowed is 2-bit (icr1 or ocr1a set to 0x0003), and the maximum resolution is 16-bit (icr1 or ocr1a set to max). the pwm resolution in bits can be calculated by using the following equation: in fast pwm mode the counter is incremented until the counter value matches either one of the fixed values 0x00ff, 0x01ff, or 0x03ff (wgm13:0 = 5, 6, or 7), the value in icr1 (wgm13:0 = 14), or the value in ocr1a (wgm13:0 = 15). the counter is then cleared at the following timer clock cycle. the timing diagram for the fast pwm mode is shown in figure 45. the figure shows fast pwm mode when ocr1a or icr1 is used to define top. the tcnt1 value is in the timing diagram shown as a histogram for illus- trating the single-slope operation. the diagram includes non-inverted and inverted pwm outputs. the small horizontal line marks on the tcnt1 slopes represent compare matches between ocr1x and tcnt1. the oc1x interrupt flag will be set when a com- pare match occurs. figure 45. fast pwm mode, timing diagram the timer/counter overflow flag (tov1) is set each time the counter reaches top. in addition the oc1a or icf1 flag is set at the same timer clock cycle as tov1 is set when either ocr1a or icr1 is used for defining the top value. if one of the interrupts are enabled, the interrupt handler routine can be used for updating the top and com- pare values. r fpwm top 1 + () log 2 () log ---------------------------------- - = tcntn ocrnx / top update and tovn interrupt flag set and ocna interrupt flag set or icfn interrupt flag set (interrupt on top) 1 7 period 2 3 4 5 6 8 ocnx ocnx (comnx1:0 = 2) (comnx1:0 = 3) 110 atmega169v/l 2514j?avr?12/03 when changing the top value the program must ensure that the new top value is higher or equal to the value of all of the compare registers. if the top value is lower than any of the compare registers, a compare match will never occur between the tcnt1 and the ocr1x. note that when using fixed top values the unused bits are masked to zero when any of the ocr1x registers are written. the procedure for updating icr1 differs from updating ocr1a when used for defining the top value. the icr1 register is not double buffered. this means that if icr1 is changed to a low value when the counter is running with none or a low prescaler value, there is a risk that the new icr1 value written is lower than the current value of tcnt1. the result will then be that the counter will miss the compare match at the top value. the counter will then have to count to the max value (0xffff) and wrap around start- ing at 0x0000 before the compare match can occur. the ocr1a register however, is double buffered. this feature allows the ocr1a i/o location to be written anytime. when the ocr1a i/o location is written the value written will be put into the ocr1a buffer register. the ocr1a compare register will then be updated with the value in the buffer register at the next timer clock cycle the tcnt1 matches top. the update is done at the same timer clock cycle as the tcnt1 is cleared and the tov1 flag is set. using the icr1 register for defining top works well when using fixed top values. by using icr1, the ocr1a register is free to be used for generating a pwm output on oc1a. however, if the base pwm frequency is actively changed (by changing the top value), using the ocr1a as top is clearly a better choice due to its double buffer feature. in fast pwm mode, the compare units allow generation of pwm waveforms on the oc1x pins. setting the com1x1:0 bits to two will produce a non-inverted pwm and an inverted pwm output can be generated by setting the com1x1:0 to three (see table on page 117). the actual oc1x value will only be visible on the port pin if the data direction for the port pin is set as output (ddr_oc1x). the pwm waveform is generated by set- ting (or clearing) the oc1x register at the compare match between ocr1x and tcnt1, and clearing (or setting) the oc1x register at the timer clock cycle the counter is cleared (changes from top to bottom). the pwm frequency for the output can be calculated by the following equation: the n variable represents the prescaler divider (1, 8, 64, 256, or 1024). the extreme values for the ocr1x register represents special cases when generating a pwm waveform output in the fast pwm mode. if the ocr1x is set equal to bottom (0x0000) the output will be a narrow spike for each top+1 timer clock cycle. setting the ocr1x equal to top will result in a constant high or low output (depending on the polar- ity of the output set by the com1x1:0 bits.) a frequency (with 50% duty cycle) waveform output in fast pwm mode can be achieved by setting oc1a to toggle its logical level on each compare match (com1a1:0 = 1). this applies only if ocr1a is used to define the top value (wgm13:0 = 15). the wave- form generated will have a maximum frequency of f oc 1 a = f clk_i/o /2 when ocr1a is set to zero (0x0000). this feature is similar to the oc1a toggle in ctc mode, except the dou- ble buffer feature of the output compare unit is enabled in the fast pwm mode. f ocnxpwm f clk_i/o n 1 top + () ? ---------------------------------- - = 111 atmega169v/l 2514j?avr?12/03 phase correct pwm mode the phase correct pulse width modulation or phase correct pwm mode (wgm13:0 = 1, 2, 3, 10, or 11) provides a high resolution phase correct pwm waveform generation option. the phase correct pwm mode is, like the phase and frequency correct pwm mode, based on a dual-slope operation. the counter counts repeatedly from bottom (0x0000) to top and then from top to bottom. in non-inverting compare output mode, the output compare (oc1x) is cleared on the compare match between tcnt1 and ocr1x while upcounting, and set on the compare match while downcounting. in inverting output compare mode, the operation is inverted. the dual-slope operation has lower maximum operation frequency than single slope operation. however, due to the symmetric feature of the dual-slope pwm modes, these modes are preferred for motor control applications. the pwm resolution for the phase correct pwm mode can be fixed to 8-, 9-, or 10-bit, or defined by either icr1 or ocr1a. the minimum resolution allowed is 2-bit (icr1 or ocr1a set to 0x0003), and the maximum resolution is 16-bit (icr1 or ocr1a set to max). the pwm resolution in bits can be calculated by using the following equation: in phase correct pwm mode the counter is incremented until the counter value matches either one of the fixed values 0x00ff, 0x01ff, or 0x03ff (wgm13:0 = 1, 2, or 3), the value in icr1 (wgm13:0 = 10), or the value in ocr1a (wgm13:0 = 11). the counter has then reached the top and changes the count direction. the tcnt1 value will be equal to top for one timer clock cycle. the timing diagram for the phase correct pwm mode is shown on figure 46. the figure shows phase correct pwm mode when ocr1a or icr1 is used to define top. the tcnt1 value is in the timing diagram shown as a histogram for illustrating the dual-slope operation. the diagram includes non-inverted and inverted pwm outputs. the small horizontal line marks on the tcnt1 slopes repre- sent compare matches between ocr1x and tcnt1. the oc1x interrupt flag will be set when a compare match occurs. figure 46. phase correct pwm mode, timing diagram the timer/counter overflow flag (tov1) is set each time the counter reaches bot- tom. when either ocr1a or icr1 is used for defining the top value, the oc1a or r pcpwm top 1 + () log 2 () log ---------------------------------- - = ocrnx/top update and ocna interrupt flag set or icfn interrupt flag set (interrupt on top) 1 2 3 4 tovn interrupt flag set (interrupt on bottom) tcntn period ocnx ocnx (comnx1:0 = 2) (comnx1:0 = 3) 112 atmega169v/l 2514j?avr?12/03 icf1 flag is set accordingly at the same timer clock cycle as the ocr1x registers are updated with the double buffer value (at top). the interrupt flags can be used to gen- erate an interrupt each time the counter reaches the top or bottom value. when changing the top value the program must ensure that the new top value is higher or equal to the value of all of the compare registers. if the top value is lower than any of the compare registers, a compare match will never occur between the tcnt1 and the ocr1x. note that when using fixed top values, the unused bits are masked to zero when any of the ocr1x registers are written. as the third period shown in figure 46 illustrates, changing the top actively while the timer/counter is running in the phase correct mode can result in an unsymmetrical output. the reason for this can be found in the time of update of the ocr1x register. since the ocr1x update occurs at top, the pwm period starts and ends at top. this implies that the length of the fall- ing slope is determined by the previous top value, while the length of the rising slope is determined by the new top value. when these two values differ the two slopes of the period will differ in length. the difference in length gives the unsymmetrical result on the output. it is recommended to use the phase and frequency correct mode instead of the phase correct mode when changing the top value while the timer/counter is running. when using a static top value there are practically no differences between the two modes of operation. in phase correct pwm mode, the compare units allow generation of pwm waveforms on the oc1x pins. setting the com1x1:0 bits to two will produce a non-inverted pwm and an inverted pwm output can be generated by setting the com1x1:0 to three (see table on page 118). the actual oc1x value will only be visible on the port pin if the data direc- tion for the port pin is set as output (ddr_oc1x). the pwm waveform is generated by setting (or clearing) the oc1x register at the compare match between ocr1x and tcnt1 when the counter increments, and clearing (or setting) the oc1x register at compare match between ocr1x and tcnt1 when the counter decrements. the pwm frequency for the output when using phase correct pwm can be calculated by the fol- lowing equation: the n variable represents the prescaler divider (1, 8, 64, 256, or 1024). the extreme values for the ocr1x register represent special cases when generating a pwm waveform output in the phase correct pwm mode. if the ocr1x is set equal to bottom the output will be continuously low and if set equal to top the output will be continuously high for non-inverted pwm mode. for inverted pwm the output will have the opposite logic values. if ocr1a is used to define the top value (wgm13:0 = 11) and com1a1:0 = 1, the oc1a output will toggle with a 50% duty cycle. f ocnxpcpwm f clk_i/o 2 ntop ?? --------------------------- - = 113 atmega169v/l 2514j?avr?12/03 phase and frequency correct pwm mode the phase and frequency correct pulse width modulation, or phase and frequency cor- rect pwm mode (wgm13:0 = 8 or 9) provides a high resolution phase and frequency correct pwm waveform generation option. the phase and frequency correct pwm mode is, like the phase correct pwm mode, based on a dual-slope operation. the counter counts repeatedly from bottom (0x0000) to top and then from top to bot- tom. in non-inverting compare output mode, the output compare (oc1x) is cleared on the compare match between tcnt1 and ocr1x while upcounting, and set on the compare match while downcounting. in inverting compare output mode, the operation is inverted. the dual-slope operation gives a lower maximum operation frequency com- pared to the single-slope operation. however, due to the symmetric feature of the dual- slope pwm modes, these modes are preferred for motor control applications. the main difference between the phase correct, and the phase and frequency correct pwm mode is the time the ocr1x register is updated by the ocr1x buffer register, (see figure 46 and figure 47). the pwm resolution for the phase and frequency correct pwm mode can be defined by either icr1 or ocr1a. the minimum resolution allowed is 2-bit (icr1 or ocr1a set to 0x0003), and the maximum resolution is 16-bit (icr1 or ocr1a set to max). the pwm resolution in bits can be calculated using the following equation: in phase and frequency correct pwm mode the counter is incremented until the counter value matches either the value in icr1 (wgm13:0 = 8), or the value in ocr1a (wgm13:0 = 9). the counter has then reached the top and changes the count direc- tion. the tcnt1 value will be equal to top for one timer clock cycle. the timing diagram for the phase correct and frequency correct pwm mode is shown on figure 47. the figure shows phase and frequency correct pwm mode when ocr1a or icr1 is used to define top. the tcnt1 value is in the timing diagram shown as a histogram for illustrating the dual-slope operation. the diagram includes non-inverted and inverted pwm outputs. the small horizontal line marks on the tcnt1 slopes represent compare matches between ocr1x and tcnt1. the oc1x interrupt flag will be set when a com- pare match occurs. figure 47. phase and frequency correct pwm mode, timing diagram r pfcpwm top 1 + () log 2 () log ---------------------------------- - = ocrnx/top updateand tovn interrupt flag set (interrupt on bottom) ocna interrupt flag set or icfn interrupt flag set (interrupt on top) 1 2 3 4 tcntn period ocnx ocnx (comnx1:0 = 2) (comnx1:0 = 3) 114 atmega169v/l 2514j?avr?12/03 the timer/counter overflow flag (tov1) is set at the same timer clock cycle as the ocr1x registers are updated with the double buffer value (at bottom). when either ocr1a or icr1 is used for defining the top value, the oc1a or icf1 flag set when tcnt1 has reached top. the interrupt flags can then be used to generate an interrupt each time the counter reaches the top or bottom value. when changing the top value the program must ensure that the new top value is higher or equal to the value of all of the compare registers. if the top value is lower than any of the compare registers, a compare match will never occur between the tcnt1 and the ocr1x. as figure 47 shows the output generated is, in contrast to the phase correct mode, sym- metrical in all periods. since the ocr1x registers are updated at bottom, the length of the rising and the falling slopes will always be equal. this gives symmetrical output pulses and is therefore frequency correct. using the icr1 register for defining top works well when using fixed top values. by using icr1, the ocr1a register is free to be used for generating a pwm output on oc1a. however, if the base pwm frequency is actively changed by changing the top value, using the ocr1a as top is clearly a better choice due to its double buffer feature. in phase and frequency correct pwm mode, the compare units allow generation of pwm waveforms on the oc1x pins. setting the com1x1:0 bits to two will produce a non-inverted pwm and an inverted pwm output can be generated by setting the com1x1:0 to three (see table on page 118). the actual oc1x value will only be visible on the port pin if the data direction for the port pin is set as output (ddr_oc1x). the pwm waveform is generated by setting (or clearing) the oc1x register at the compare match between ocr1x and tcnt1 when the counter increments, and clearing (or set- ting) the oc1x register at compare match between ocr1x and tcnt1 when the counter decrements. the pwm frequency for the output when using phase and fre- quency correct pwm can be calculated by the following equation: the n variable represents the prescaler divider (1, 8, 64, 256, or 1024). the extreme values for the ocr1x register represents special cases when generating a pwm waveform output in the phase correct pwm mode. if the ocr1x is set equal to bottom the output will be continuously low and if set equal to top the output will be set to high for non-inverted pwm mode. for inverted pwm the output will have the opposite logic values. if ocr1a is used to define the top value (wgm13:0 = 9) and com1a1:0 = 1, the oc1a output will toggle with a 50% duty cycle. f ocnxpfcpwm f clk_i/o 2 ntop ?? --------------------------- - = 115 atmega169v/l 2514j?avr?12/03 timer/counter timing diagrams the timer/counter is a synchronous design and the timer clock (clk t1 ) is therefore shown as a clock enable signal in the following figures. the figures include information on when interrupt flags are set, and when the ocr1x register is updated with the ocr1x buffer value (only for modes utilizing double buffering). figure 48 shows a timing diagram for the setting of ocf1x. figure 48. timer/counter timing diagram, setting of ocf1x, no prescaling figure 49 shows the same timing data, but with the prescaler enabled. figure 49. timer/counter timing diagram, setting of ocf1x, with prescaler (f clk_i/o /8) figure 50 shows the count sequence close to top in various modes. when using phase and frequency correct pwm mode the ocr1x register is updated at bottom. the timing diagrams will be the same, but top should be replaced by bottom, top-1 by bottom+1 and so on. the same renaming applies for modes that set the tov1 flag at bottom. clk tn (clk i/o /1) ocfnx clk i/o ocrnx tcntn ocrnx value ocrnx - 1 ocrnx ocrnx + 1 ocrnx + 2 ocfnx ocrnx tcntn ocrnx value ocrnx - 1 ocrnx ocrnx + 1 ocrnx + 2 clk i/o clk tn (clk i/o /8) 116 atmega169v/l 2514j?avr?12/03 figure 50. timer/counter timing diagram, no prescaling figure 51 shows the same timing data, but with the prescaler enabled. figure 51. timer/counter timing diagram, with prescaler (f clk_i/o /8) tovn (fpwm) and icfn (if used as top) ocrnx (update at top) tcntn (ctc and fpwm) tcntn (pc and pfc pwm) top - 1 top top - 1 top - 2 old ocrnx value new ocrnx value top - 1 top bottom bottom + 1 clk tn (clk i/o /1) clk i/o tovn (fpwm) and icf n (if used as top) ocrnx (update at top) tcntn (ctc and fpwm) tcntn (pc and pfc pwm) top - 1 top top - 1 top - 2 old ocrnx value new ocrnx value top - 1 top bottom bottom + 1 clk i/o clk tn (clk i/o /8) 117 atmega169v/l 2514j?avr?12/03 16-bit timer/counter register description timer/counter1 control register a ? tccr1a bit 7:6 ? com1a1:0: compare output mode for channel a bit 5:4 ? com1b1:0: compare output mode for channel b the com1a1:0 and com1b1:0 control the output compare pins (oc1a and oc1b respectively) behavior. if one or both of the com1a1:0 bits are written to one, the oc1a output overrides the normal port functionality of the i/o pin it is connected to. if one or both of the com1b1:0 bit are written to one, the oc1b output overrides the normal port functionality of the i/o pin it is connected to. however, note that the data direction reg- ister (ddr) bit corresponding to the oc1a or oc1b pin must be set in order to enable the output driver. when the oc1a or oc1b is connected to the pin, the function of the com1x1:0 bits is dependent of the wgm13:0 bits setting. table 55 shows the com1x1:0 bit functionality when the wgm13:0 bits are set to a normal or a ctc mode (non-pwm). table 56 shows the com1x1:0 bit functionality when the wgm13:0 bits are set to the fast pwm mode. note: 1. a special case occurs when ocr1a/ocr1b equals top and com1a1/com1b1 is set. in this case the compare match is ig nored, but the set or clear is done at top. see ?fast pwm mode? on page 109. for more details. bit 7 6 5 4 3 2 1 0 com1a1 com1a0 com1b1 com1b0 ? ? wgm11 wgm10 tccr1a read/write r/w r/w r/w r/w r r r/w r/w initial value 0 0 0 0 0 0 0 0 table 55. compare output mode, non-pwm com1a1/com1b1 com1a0/com1b0 description 0 0 normal port operation, oc1a/oc1b disconnected. 0 1 toggle oc1a/oc1b on compare match. 1 0 clear oc1a/oc1b on compare match (set output to low level). 1 1 set oc1a/oc1b on compare match (set output to high level). table 56. compare output mode, fast pwm (1) com1a1/com1b1 com1a0/com1b0 description 0 0 normal port operation, oc1a/oc1b disconnected. 0 1 wgm13:0 = 15: toggle oc1a on compare match, oc1b disconnected (normal port operation). for all other wgm1 settings, normal port operation, oc1a/oc1b disconnected. 1 0 clear oc1a/oc1b on compare match, set oc1a/oc1b at top 1 1 set oc1a/oc1b on compare match, clear oc1a/oc1b at top 118 atmega169v/l 2514j?avr?12/03 table 57 shows the com1x1:0 bit functionality when the wgm13:0 bits are set to the phase correct or the phase and frequency correct, pwm mode. note: 1. a special case occurs when ocr1a/ocr1b equals top and com1a1/com1b1 is set. see ?phase correct pwm mode? on page 111. for more details. bit 1:0 ? wgm11:0: waveform generation mode combined with the wgm13:2 bits found in the tccr1b register, these bits control the counting sequence of the counter, the source for maximum (top) counter value, and what type of waveform generation to be used, see table 58. modes of operation sup- ported by the timer/counter unit are: normal mode (counter), clear timer on compare match (ctc) mode, and three types of pulse width modulation (pwm) modes. (see ?modes of operation? on page 107.). table 57. compare output mode, phase correct and phase and frequency correct pwm (1) com1a1/com1b1 com1a0/com1b0 description 0 0 normal port operation, oc1a/oc1b disconnected. 0 1 wgm13:0 = 9 or 14: toggle oc1a on compare match, oc1b disconnected (normal port operation). for all other wgm1 settings, normal port operation, oc1a/oc1b disconnected. 1 0 clear oc1a/oc1b on compare match when up- counting. set oc1a/oc1b on compare match when downcounting. 1 1 set oc1a/oc1b on compare match when up- counting. clear oc1a/oc1b on compare match when downcounting. 119 atmega169v/l 2514j?avr?12/03 note: 1. the ctc1 and pwm11:0 bit definition names are obsolete. use the wgm 12:0 definitions. however, the functionality and location of these bits are compatible with previous versions of the timer. timer/counter1 control register b ? tccr1b bit 7 ? icnc1: input capture noise canceler setting this bit (to one) activates the input capture noise canceler. when the noise can- celer is activated, the input from the input capture pin (icp1) is filtered. the filter function requires four successive equal valued samples of the icp1 pin for changing its output. the input capture is therefore delayed by four oscillator cycles when the noise canceler is enabled. bit 6 ? ices1: input capture edge select this bit selects which edge on the input capture pin (icp1) that is used to trigger a cap- ture event. when the ices1 bit is written to zero, a falling (negative) edge is used as trigger, and when the ices1 bit is written to one, a rising (positive) edge will trigger the capture. when a capture is triggered according to the ices1 setting, the counter value is copied into the input capture register (icr1). the event will also set the input capture flag table 58. waveform generation mode bit description (1) mode wgm13 wgm12 (ctc1) wgm11 (pwm11) wgm10 (pwm10) timer/counter mode of operation top update of ocr1 x at tov1 flag set on 0 0 0 0 0 normal 0xffff immediate max 1 0 0 0 1 pwm, phase correct, 8-bit 0x00ff top bottom 2 0 0 1 0 pwm, phase correct, 9-bit 0x01ff top bottom 3 0 0 1 1 pwm, phase correct, 10-bit 0x03ff top bottom 40100ctc ocr1aimmediatemax 5 0 1 0 1 fast pwm, 8-bit 0x00ff top top 6 0 1 1 0 fast pwm, 9-bit 0x01ff top top 7 0 1 1 1 fast pwm, 10-bit 0x03ff top top 8 1 0 0 0 pwm, phase and frequency correct icr1 bottom bottom 9 1 0 0 1 pwm, phase and frequency correct ocr1a bottom bottom 10 1 0 1 0 pwm, phase correct icr1 top bottom 11 1 0 1 1 pwm, phase correct ocr1a top bottom 12 1 1 0 0 ctc icr1 immediate max 131101(reserved) ? ? ? 141110fast pwm icr1toptop 15 1 1 1 1 fast pwm ocr1a top top bit 7654 3210 icnc1 ices1 ? wgm13 wgm12 cs12 cs11 cs10 tccr1b read/write r/w r/w r r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 120 atmega169v/l 2514j?avr?12/03 (icf1), and this can be used to cause an input capture interrupt, if this interrupt is enabled. when the icr1 is used as top value (see description of the wgm13:0 bits located in the tccr1a and the tccr1b register), the icp1 is disconnected and consequently the input capture function is disabled. bit 5 ? reserved bit this bit is reserved for future use. for ensuring compatibility with future devices, this bit must be written to zero when tccr1b is written. bit 4:3 ? wgm13:2: waveform generation mode see tccr1a register description. bit 2:0 ? cs12:0: clock select the three clock select bits select the clock source to be used by the timer/counter, see figure 48 and figure 49. if external pin modes are used for the timer/counter1, transitions on the t1 pin will clock the counter even if the pin is configured as an output. this feature allows software control of the counting. timer/counter1 control register c ? tccr1c bit 7 ? foc1a: force output compare for channel a bit 6 ? foc1b: force output compare for channel b the foc1a/foc1b bits are only active when the wgm13:0 bits specifies a non-pwm mode. however, for ensuring compatibility with future devices, these bits must be set to zero when tccr1a is written when operating in a pwm mode. when writing a logical one to the foc1a/foc1b bit, an immediate compare match is forced on the waveform generation unit. the oc1a/oc1b output is changed according to its com1x1:0 bits setting. note that the foc1a/foc1b bits are implemented as strobes. therefore it is the value present in the com1x1:0 bits that determine the effect of the forced compare. table 59. clock select bit description cs12 cs11 cs10 description 0 0 0 no clock source (timer/counter stopped). 001clk i/o /1 (no prescaling) 010clk i/o /8 (from prescaler) 011clk i/o /64 (from prescaler) 100clk i/o /256 (from prescaler) 101clk i/o /1024 (from prescaler) 1 1 0 external clock source on t1 pin. clock on falling edge. 1 1 1 external clock source on t1 pin. clock on rising edge. bit 7654 3210 foc1a foc1b ? ? ? ? ? ? tccr1c read/write r/w r/w r r r r r r initial value 0 0 0 0 0 0 0 0 121 atmega169v/l 2514j?avr?12/03 a foc1a/foc1b strobe will not generate any interrupt nor will it clear the timer in clear timer on compare match (ctc) mode using ocr1a as top. the foc1a/foc1b bits are always read as zero. timer/counter1 ? tcnt1h and tcnt1l the two timer/counter i/o locations (tcnt1h and tcnt1l, combined tcnt1) give direct access, both for read and for write operations, to the timer/counter unit 16-bit counter. to ensure that both the high and low bytes are read and written simultaneously when the cpu accesses these registers, the access is performed using an 8-bit tempo- rary high byte register (temp). this temporary register is shared by all the other 16-bit registers. see ?accessing 16-bit registers? on page 98. modifying the counter (tcnt1) while the counter is running introduces a risk of missing a compare match between tcnt1 and one of the ocr1x registers. writing to the tcnt1 register blocks (removes) the compare match on the following timer clock for all compare units. output compare register 1 a ? ocr1ah and ocr1al output compare register 1 b ? ocr1bh and ocr1bl the output compare registers contain a 16-bit value that is continuously compared with the counter value (tcnt1). a match can be used to generate an output compare interrupt, or to generate a waveform output on the oc1x pin. the output compare registers are 16-bit in size. to ensure that both the high and low bytes are written simultaneously when the cpu writes to these registers, the access is performed using an 8-bit temporary high byte register (temp). this temporary register is shared by all the other 16-bit registers. see ?accessing 16-bit registers? on page 98. bit 76543210 tcnt1[15:8] tcnt1h tcnt1[7:0] tcnt1l read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 ocr1a[15:8] ocr1ah ocr1a[7:0] ocr1al read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 ocr1b[15:8] ocr1bh ocr1b[7:0] ocr1bl read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 122 atmega169v/l 2514j?avr?12/03 input capture register 1 ? icr1h and icr1l the input capture is updated with the counter (tcnt1) value each time an event occurs on the icp1 pin (or optionally on the analog comparator output for timer/counter1). the input capture can be used for defining the counter top value. the input capture register is 16-bit in size. to ensure that both the high and low bytes are read simultaneously when the cpu accesses these registers, the access is per- formed using an 8-bit temporary high byte r egister (temp). this temporary register is shared by all the other 16-bit registers. see ?accessing 16-bit registers? on page 98. timer/counter1 interrupt mask register ? timsk1 bit 5 ? icie1: timer/counter1, input capture interrupt enable when this bit is written to one, and the i-flag in the status register is set (interrupts glo- bally enabled), the timer/counter1 input capture interrupt is enabled. the corresponding interrupt vector (see ?interrupts? on page 46.) is executed when the icf1 flag, located in tifr1, is set. bit 2 ? ocie1b: timer/counter1, output compare b match interrupt enable when this bit is written to one, and the i-flag in the status register is set (interrupts glo- bally enabled), the timer/counter1 output compare b match interrupt is enabled. the corresponding interrupt vector (see ?interrupts? on page 46.) is executed when the ocf1b flag, located in tifr1, is set. bit 1 ? ocie1a: timer/counter1, output compare a match interrupt enable when this bit is written to one, and the i-flag in the status register is set (interrupts glo- bally enabled), the timer/counter1 output compare a match interrupt is enabled. the corresponding interrupt vector (see ?interrupts? on page 46.) is executed when the ocf1a flag, located in tifr1, is set. bit 0 ? toie1: timer/counter1, overflow interrupt enable when this bit is written to one, and the i-flag in the status register is set (interrupts glo- bally enabled), the timer/counter1 overflow interrupt is enabled. the corresponding interrupt vector (see ?interrupts? on page 46.) is executed when the tov1 flag, located in tifr1, is set. bit 76543210 icr1[15:8] icr1h icr1[7:0] icr1l read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 ? ?icie1 ? ? ocie1b ocie1a toie1 timsk1 read/write r r r/w r r r/w r/w r/w initial value 0 0 0 0 0 0 0 0 123 atmega169v/l 2514j?avr?12/03 timer/counter1 interrupt flag register ? tifr1 bit 5 ? icf1: timer/counter1, input capture flag this flag is set when a capture event occurs on the icp1 pin. when the input capture register (icr1) is set by the wgm13:0 to be used as the top value, the icf1 flag is set when the counter reaches the top value. icf1 is automatically cleared when the input capture interrupt vector is executed. alter- natively, icf1 can be cleared by writing a logic one to its bit location. bit 2 ? ocf1b: timer/counter1, output compare b match flag this flag is set in the timer clock cycle after the counter (tcnt1) value matches the out- put compare register b (ocr1b). note that a forced output compare (foc1b) strobe will not set the ocf1b flag. ocf1b is automatically cleared when the output compare match b interrupt vector is executed. alternatively, ocf1b can be cleared by writing a logic one to its bit location. bit 1 ? ocf1a: timer/counter1, output compare a match flag this flag is set in the timer clock cycle after the counter (tcnt1) value matches the out- put compare register a (ocr1a). note that a forced output compare (foc1a) strobe will not set the ocf1a flag. ocf1a is automatically cleared when the output compare match a interrupt vector is executed. alternatively, ocf1a can be cleared by writing a logic one to its bit location. bit 0 ? tov1: timer/counter1, overflow flag the setting of this flag is dependent of the wgm13:0 bits setting. in normal and ctc modes, the tov1 flag is set when the timer overflows. refer to table 58 on page 119 for the tov1 flag behavior when using another wgm13:0 bit setting. tov1 is automatically cleared when the timer/counter1 overflow interrupt vector is executed. alternatively, tov1 can be cleared by writing a logic one to its bit location. bit 76543210 ? ?icf1 ? ? ocf1b ocf1a tov1 tifr1 read/write r r r/w r r r/w r/w r/w initial value00000000 124 atmega169v/l 2514j?avr?12/03 8-bit timer/counter2 with pwm and asynchronous operation timer/counter2 is a general purpose, single channel, 8-bit timer/counter module. the main features are: single channel counter clear timer on compare match (auto reload) glitch-free, phase correct pulse width modulator (pwm) frequency generator 10-bit clock prescaler overflow and compare match interrupt sources (tov2 and ocf2a) allows clocking from external 32 khz watch crystal independent of the i/o clock overview a simplified block diagram of the 8-bit timer/counter is shown in figure 52. for the actual placement of i/o pins, refer to ?pinout atmega169? on page 2. cpu accessible i/o registers, including i/o bits and i/o pins, are shown in bold. the device-specific i/o register and bit locations are listed in the ?8-bit timer/counter register description? on page 135. figure 52. 8-bit timer/counter block diagram registers the timer/counter (tcnt2) and output compare register (ocr2a) are 8-bit registers. interrupt request (shorten as int.req.) signals are all visible in the timer interrupt flag register (tifr2). all interrupts are individually masked with the timer interrupt mask register (timsk2). tifr2 and timsk2 are not shown in the figure. the timer/counter can be clocked internally, via the prescaler, or asynchronously clocked from the tosc1/2 pins, as detailed later in this section. the asynchronous operation is controlled by the asynchronous status register (assr). the clock select logic block controls which clock source the timer/counter uses to increment (or decre- timer/counter data b u s = tcntn waveform generation ocnx = 0 control logic = 0xff top bottom count clear direction tovn (int.req.) ocnx (int.req.) synchronization unit ocrnx tccrnx assrn status flags clk i/o clk asy synchronized status flags asynchronous mode select (asn) tosc1 t/c oscillator tosc2 prescaler clk tn clk i/o 125 atmega169v/l 2514j?avr?12/03 ment) its value. the timer/counter is inactive when no clock source is selected. the output from the clock select logic is referred to as the timer clock (clk t2 ). the double buffered output compare register (ocr2a) is compared with the timer/counter value at all times. the result of the compare can be used by the wave- form generator to generate a pwm or variable frequency output on the output compare pin (oc2a). see ?output compare unit? on page 126. for details. the compare match event will also set the compare flag (ocf2a) which can be used to generate an output compare interrupt request. definitions many register and bit references in this do cument are written in general form. a lower case ?n? replaces the timer/counter number, in this case 2. however, when using the register or bit defines in a program, the pr ecise form must be used, i.e., tcnt2 for accessing timer/counter2 counter value and so on. the definitions in table 60 are also used extensively throughout the section. timer/counter clock sources the timer/counter can be clocked by an internal synchronous or an external asynchro- nous clock source. the clock source clk t2 is by default equal to the mcu clock, clk i/o . when the as2 bit in the assr register is written to logic one, the clock source is taken from the timer/counter oscillator connected to tosc1 and tosc2. for details on asynchronous operation, see ?asynchronous status register ? assr? on page 138. for details on clock sources and prescaler, see ?timer/counter prescaler? on page 142. counter unit the main part of the 8-bit timer/counter is the programmable bi-directional counter unit. figure 53 shows a block diagram of the counter and its surrounding environment. figure 53. counter unit block diagram signal description (internal signals): count increment or decrement tcnt2 by 1. direction selects between increment and decrement. clear clear tcnt2 (set all bits to zero). clk t 2 timer/counter clock. table 60. definitions bottom the counter reaches the bottom when it becomes zero (0x00). max the counter reaches its maximum when it becomes 0xff (decimal 255). top the counter reaches the top when it becomes equal to the highest value in the count sequence. the top value can be assigned to be the fixed value 0xff (max) or the value stored in the ocr2a register. the assignment is dependent on the mode of operation. data b u s tcntn control logic count tovn (int.req.) top bottom direction clear tosc1 t/c oscillator tosc2 prescaler clk i/o clk tn 126 atmega169v/l 2514j?avr?12/03 top signalizes that tcnt2 has reached maximum value. bottom signalizes that tcnt2 has reached minimum value (zero). depending on the mode of operation used, the counter is cleared, incremented, or dec- remented at each timer clock (clk t2 ). clk t2 can be generated from an external or internal clock source, selected by the clock select bits (cs22:0). when no clock source is selected (cs22:0 = 0) the timer is stopped. however, the tcnt2 value can be accessed by the cpu, regardless of whether clk t2 is present or not. a cpu write overrides (has priority over) all counter clear or count operations. the counting sequence is determined by the setting of the wgm21 and wgm20 bits located in the timer/counter control register (tccr2a). there are close connections between how the counter behaves (counts) and how waveforms are generated on the output compare output oc2a. for more details about advanced counting sequences and waveform generation, see ?modes of operation? on page 129. the timer/counter overflow flag (tov2) is set according to the mode of operation selected by the wgm21:0 bits. tov2 can be used for generating a cpu interrupt. output compare unit the 8-bit comparator continuously compares tcnt2 with the output compare register (ocr2a). whenever tcnt2 equals ocr2a, the comparator signals a match. a match will set the output compare flag (ocf2a) at the next timer clock cycle. if enabled (ocie2a = 1), the output compare flag generates an output compare interrupt. the ocf2a flag is automatically cleared when the interrupt is executed. alternatively, the ocf2a flag can be cleared by software by writing a logical one to its i/o bit location. the waveform generator uses the match signal to generate an output according to operating mode set by the wgm21:0 bits and compare output mode (com2a1:0) bits. the max and bottom signals are used by the waveform generator for handling the spe- cial cases of the extreme values in some modes of operation (?modes of operation? on page 129). figure 54 shows a block diagram of the output compare unit. figure 54. output compare unit, block diagram ocfn x (int.req.) = (8-bit comparator ) ocrnx ocnx data b u s tcntn wgmn1:0 waveform generator top focn comnx1:0 bottom 127 atmega169v/l 2514j?avr?12/03 the ocr2a register is double buffered when using any of the pulse width modulation (pwm) modes. for the normal and clear timer on compare (ctc) modes of operation, the double buffering is disabled. the double buffering synchronizes the update of the ocr2a compare register to either top or bottom of the counting sequence. the syn- chronization prevents the occurrence of odd-length, non-symmetrical pwm pulses, thereby making the output glitch-free. the ocr2a register access may seem complex, but this is not case. when the double buffering is enabled, the cpu has access to the ocr2a buffer register, and if double buffering is disabled the cpu will access the ocr2a directly. force output compare in non-pwm waveform generation modes, the match output of the comparator can be forced by writing a one to the force output compare (foc2a) bit. forcing compare match will not set the ocf2a flag or reload/clear the timer, but the oc2a pin will be updated as if a real compare match had occurred (the com2a1:0 bits settings define whether the oc2a pin is set, cleared or toggled). compare match blocking by tcnt2 write all cpu write operations to the tcnt2 register will block any compare match that occurs in the next timer clock cycle, even when the timer is stopped. this feature allows ocr2a to be initialized to the same value as tcnt2 without triggering an interrupt when the timer/counter clock is enabled. using the output compare unit since writing tcnt2 in any mode of operation will block all compare matches for one timer clock cycle, there are risks involved when changing tcnt2 when using the output compare channel, independently of whether the ti mer/counter is running or not. if the value written to tcnt2 equals the ocr2a value, the compare match will be missed, resulting in incorrect waveform generation. similarly, do not write the tcnt2 value equal to bottom when the counter is downcounting. the setup of the oc2a should be performed before setting the data direction register for the port pin to output. the easiest way of setting the oc2a value is to use the force output compare (foc2a) strobe bit in normal mode. the oc2a register keeps its value even when changing between waveform generation modes. be aware that the com2a1:0 bits are not double buffered together with the compare value. changing the com2a1:0 bits will take effect immediately. 128 atmega169v/l 2514j?avr?12/03 compare match output unit the compare output mode (com2a1:0) bits have two functions. the waveform gener- ator uses the com2a1:0 bits for defining the output compare (oc2a) state at the next compare match. also, the com2a1:0 bits control the oc2a pin output source. figure 55 shows a simplified schematic of the logic affected by the com2a1:0 bit setting. the i/o registers, i/o bits, and i/o pins in the figure are shown in bold. only the parts of the general i/o port control registers (ddr and port) that are affected by the com2a1:0 bits are shown. when referring to the oc2a state, the reference is for the internal oc2a register, not the oc2a pin. figure 55. compare match output unit, schematic the general i/o port function is overridden by the output compare (oc2a) from the waveform generator if either of the com2a1:0 bits are set. however, the oc2a pin direction (input or output) is still controlled by the data direction register (ddr) for the port pin. the data direction register bit for the oc2a pin (ddr_oc2a) must be set as output before the oc2a value is visible on the pin. the port override function is indepen- dent of the waveform generation mode. the design of the output compare pin logic allows initialization of the oc2a state before the output is enabled. note that some com2a1:0 bit settings are reserved for certain modes of operation. see ?8-bit timer/counter register description? on page 135. compare output mode and waveform generation the waveform generator uses the com2a1:0 bits differently in normal, ctc, and pwm modes. for all modes, setting the com2a1:0 = 0 tells the waveform generator that no action on the oc2a register is to be performed on the next compare match. for com- pare output actions in the non-pwm modes refer to table 62 on page 136. for fast pwm mode, refer to table 63 on page 136, and for phase correct pwm refer to table 64 on page 136. a change of the com2a1:0 bits state will have effect at the first compare match after the bits are written. for non-pwm modes, the action can be forced to have immediate effect by using the foc2a strobe bits. port ddr dq dq ocnx pin ocnx dq waveform generator comnx1 comnx0 0 1 data b u s focnx clk i/o 129 atmega169v/l 2514j?avr?12/03 modes of operation the mode of operation, i.e., the behavior of the timer/counter and the output compare pins, is defined by the combination of the waveform generation mode (wgm21:0) and compare output mode (com2a1:0) bits. the compare output mode bits do not affect the counting sequence, while the waveform generation mode bits do. the com2a1:0 bits control whether the pwm output generated should be inverted or not (inverted or non-inverted pwm). for non-pwm modes the com2a1:0 bits control whether the out- put should be set, cleared, or toggled at a compare match (see ?compare match output unit? on page 128.). for detailed timing information refer to ?timer/counter timing diagrams? on page 133. normal mode the simplest mode of operation is the normal mode (wgm21:0 = 0). in this mode the counting direction is always up (incrementing), and no counter clear is performed. the counter simply overruns when it passes its maximum 8-bit value (top = 0xff) and then restarts from the bottom (0x00). in normal operation the timer/counter overflow flag (tov2) will be set in the same timer clock cycle as the tcnt2 becomes zero. the tov2 flag in this case behaves like a ninth bit, except that it is only set, not cleared. however, combined with the timer overflow interrupt that automatically clears the tov2 flag, the timer resolution can be increased by software. there are no special cases to consider in the normal mode, a new counter value can be written anytime. the output compare unit can be used to generate interrupts at some given time. using the output compare to generate waveforms in normal mode is not recommended, since this will occupy too much of the cpu time. clear timer on compare match (ctc) mode in clear timer on compare or ctc mode (wgm21:0 = 2), the ocr2a register is used to manipulate the counter resolution. in ctc mode the counter is cleared to zero when the counter value (tcnt2) matches the ocr2a. the ocr2a defines the top value for the counter, hence also its resolution. this mode allows greater control of the compare match output frequency. it also simplifies the operation of counting external events. the timing diagram for the ctc mode is shown in figure 56. the counter value (tcnt2) increases until a compare match occurs between tcnt2 and ocr2a, and then counter (tcnt2) is cleared. figure 56. ctc mode, timing diagram an interrupt can be generated each time the counter value reaches the top value by using the ocf2a flag. if the interrupt is enabled, the interrupt handler routine can be used for updating the top value. however, changing the top to a value close to bot- tom when the counter is running with none or a low prescaler value must be done with care since the ctc mode does not have the double buffering feature. if the new value written to ocr2a is lower than the current value of tcnt2, the counter will miss the tcntn ocnx (toggle) ocnx interrupt flag set 1 4 period 2 3 (comnx1:0 = 1) 130 atmega169v/l 2514j?avr?12/03 compare match. the counter will then have to count to its maximum value (0xff) and wrap around starting at 0x00 before the compare match can occur. for generating a waveform output in ctc mode, the oc2a output can be set to toggle its logical level on each compare match by setting the compare output mode bits to tog- gle mode (com2a1:0 = 1). the oc2a value will not be visible on the port pin unless the data direction for the pin is set to output. the waveform generated will have a maximum frequency of f oc2a = f clk_i/o /2 when ocr2a is set to zero (0x00). the waveform fre- quency is defined by the following equation: the n variable represents the prescale factor (1, 8, 32, 64, 128, 256, or 1024). as for the normal mode of operation, the tov2 flag is set in the same timer clock cycle that the counter counts from max to 0x00. fast pwm mode the fast pulse width modulation or fast pwm mode (wgm21:0 = 3) provides a high fre- quency pwm waveform generation option. the fast pwm differs from the other pwm option by its single-slope operation. the counter counts from bottom to max then restarts from bottom. in non-inverting compare output mode, the output compare (oc2a) is cleared on the compare match between tcnt2 and ocr2a, and set at bot- tom. in inverting compare output mode, the output is set on compare match and cleared at bottom. due to the single-slope operation, the operating frequency of the fast pwm mode can be twice as high as the phase correct pwm mode that uses dual- slope operation. this high frequency makes the fast pwm mode well suited for power regulation, rectification, and dac applications. high frequency allows physically small sized external components (coils, capacitors), and therefore reduces total system cost. in fast pwm mode, the counter is incremented until the counter value matches the max value. the counter is then cleared at the following timer clock cycle. the timing diagram for the fast pwm mode is shown in figure 57. the tcnt2 value is in the timing diagram shown as a histogram for illustrating the single-slope operation. the diagram includes non-inverted and inverted pwm outputs. the small horizontal line marks on the tcnt2 slopes represent compare matches between ocr2a and tcnt2. figure 57. fast pwm mode, timing diagram f ocnx f clk_i/o 2 n 1 ocrnx + () ?? ------------------------------------------------- - = tcntn ocrnx update and tovn interrupt flag set 1 period 2 3 ocnx ocnx (comnx1:0 = 2) (comnx1:0 = 3) ocrnx interrupt flag set 4 5 6 7 131 atmega169v/l 2514j?avr?12/03 the timer/counter overflow flag (tov2) is set each time the counter reaches max. if the interrupt is enabled, the interrupt handler routine can be used for updating the com- pare value. in fast pwm mode, the compare unit allows generation of pwm waveforms on the oc2a pin. setting the com2a1:0 bits to two will produce a non-inverted pwm and an inverted pwm output can be generated by setting the com2a1:0 to three (see table 63 on page 136). the actual oc2a value will only be visible on the port pin if the data direc- tion for the port pin is set as output. the pwm waveform is generated by setting (or clearing) the oc2a register at the compare match between ocr2a and tcnt2, and clearing (or setting) the oc2a register at the timer clock cycle the counter is cleared (changes from max to bottom). the pwm frequency for the output can be calculated by the following equation: the n variable represents the prescale factor (1, 8, 32, 64, 128, 256, or 1024). the extreme values for the ocr2a register represent special cases when generating a pwm waveform output in the fast pwm mode. if the ocr2a is set equal to bottom, the output will be a narrow spike for each max+1 timer clock cycle. setting the ocr2a equal to max will result in a constantly high or low output (depending on the polarity of the output set by the com2a1:0 bits.) a frequency (with 50% duty cycle) waveform output in fast pwm mode can be achieved by setting oc2a to toggle its logical level on each compare match (com2a1:0 = 1). the waveform generated will have a maximum frequency of f oc2 = f clk_i/o /2 when ocr2a is set to zero. this feature is similar to the oc2a toggle in ctc mode, except the double buffer feature of the output compare unit is enabled in the fast pwm mode. phase correct pwm mode the phase correct pwm mode (wgm21:0 = 1) provides a high resolution phase correct pwm waveform generation option. the phase correct pwm mode is based on a dual- slope operation. the counter counts repeatedly from bottom to max and then from max to bottom. in non-inverting compare output mode, the output compare (oc2a) is cleared on the compare match between tcnt2 and ocr2a while upcounting, and set on the compare match while downcounting. in inverting output compare mode, the operation is inverted. the dual-slope operation has lower maximum operation frequency than single slope operation. however, due to the symmetric feature of the dual-slope pwm modes, these modes are preferred for motor control applications. the pwm resolution for the phase correct pwm mode is fixed to eight bits. in phase correct pwm mode the counter is incremented until the counter value matches max. when the counter reaches max, it changes the count direction. the tcnt2 value will be equal to max for one timer clock cycle. the timing diagram for the phase correct pwm mode is shown on figure 58. the tcnt2 value is in the timing diagram shown as a histogram for illustrating the dual-slope operation. the diagram includes non-inverted and inverted pwm outputs. the small horizontal line marks on the tcnt2 slopes repre- sent compare matches between ocr2a and tcnt2. f ocnxpwm f clk_i/o n 256 ? ------------------ = 132 atmega169v/l 2514j?avr?12/03 figure 58. phase correct pwm mode, timing diagram the timer/counter overflow flag (tov2) is set each time the counter reaches bot- tom. the interrupt flag can be used to generate an interrupt each time the counter reaches the bottom value. in phase correct pwm mode, the compare unit allows generation of pwm waveforms on the oc2a pin. setting the com2a1:0 bits to two will produce a non-inverted pwm. an inverted pwm output can be generated by setting the com2a1:0 to three (see table 64 on page 136). the actual oc2a value will only be visible on the port pin if the data direc- tion for the port pin is set as output. the pwm waveform is generated by clearing (or setting) the oc2a register at the compare match between ocr2a and tcnt2 when the counter increments, and setting (or cleari ng) the oc2a register at compare match between ocr2a and tcnt2 when the counter decrements. the pwm frequency for the output when using phase correct pwm can be calculated by the following equation: the n variable represents the prescale factor (1, 8, 32, 64, 128, 256, or 1024). the extreme values for the ocr2a register represent special cases when generating a pwm waveform output in the phase correct pwm mode. if the ocr2a is set equal to bottom, the output will be continuously low and if set equal to max the output will be continuously high for non-inverted pwm mode. for inverted pwm the output will have the opposite logic values. at the very start of period 2 in figure 58 ocn has a transition from high to low even though there is no compare match. the point of this transition is to guarantee symmetry around bottom. there are two cases that give a transition without compare match. ocr2a changes its value from max, like in figure 58. when the ocr2a value is max the ocn pin value is the same as the result of a down-counting compare match. to ensure symmetry around bottom the ocn value at max must correspond to the result of an up-counting compare match. tovn interrupt flag set ocnx interrupt flag set 1 2 3 tcntn period ocnx ocnx (comnx1:0 = 2) (comnx1:0 = 3) ocrnx update f ocnxpcpwm f clk_i/o n 510 ? ------------------ = 133 atmega169v/l 2514j?avr?12/03 the timer starts counting from a value higher than the one in ocr2a, and for that reason misses the compare match and hence the ocn change that would have happened on the way up. timer/counter timing diagrams the following figures show the timer/counter in synchronous mode, and the timer clock (clk t2 ) is therefore shown as a clock enable signal. in asynchronous mode, clk i/o should be replaced by the timer/counter oscillator clock. the figures include information on when interrupt flags are set. figure 59 contains timing data for basic timer/counter operation. the figure shows the count sequence close to the max value in all modes other than phase correct pwm mode. figure 59. timer/counter timing diagram, no prescaling figure 60 shows the same timing data, but with the prescaler enabled. figure 60. timer/counter timing diagram, with prescaler (f clk_i/o /8) figure 61 shows the setting of ocf2a in all modes except ctc mode. clk tn (clk i/o /1) tovn clk i/o tcntn max - 1 max bottom bottom + 1 tovn tcntn max - 1 max bottom bottom + 1 clk i/o clk tn (clk i/o /8) 134 atmega169v/l 2514j?avr?12/03 figure 61. timer/counter timing diagram, setting of ocf2a, with prescaler (f clk_i/o /8) figure 62 shows the setting of ocf2a and the clearing of tcnt2 in ctc mode. figure 62. timer/counter timing diagram, clear timer on compare match mode, with prescaler (f clk_i/o /8) ocfnx ocrnx tcntn ocrnx value ocrnx - 1 ocrnx ocrnx + 1 ocrnx + 2 clk i/o clk tn (clk i/o /8) ocfnx ocrnx tcntn (ctc) top top - 1 top bottom bottom + 1 clk i/o clk tn (clk i/o /8) 135 atmega169v/l 2514j?avr?12/03 8-bit timer/counter register description timer/counter control register a? tccr2a bit 7 ? foc2a: force output compare a the foc2a bit is only active when the wgm bits specify a non-pwm mode. however, for ensuring compatibility with future devices, this bit must be set to zero when tccr2a is written when operating in pwm mode. when writing a logical one to the foc2a bit, an immediate compare match is forced on the waveform generation unit. the oc2a output is changed according to its com2a1:0 bits setting. note that the foc2a bit is implemented as a strobe. therefore it is the value present in the com2a1:0 bits that determines the effect of the forced compare. a foc2a strobe will not generate any interrupt, nor will it clear the timer in ctc mode using ocr2a as top. the foc2a bit is always read as zero. bit 6, 3 ? wgm21:0: waveform generation mode these bits control the counting sequence of the counter, the source for the maximum (top) counter value, and what type of waveform generation to be used. modes of oper- ation supported by the timer/counter unit are: normal mode, clear timer on compare match (ctc) mode, and two types of pulse width modulation (pwm) modes. see table 61 and ?modes of operation? on page 129. note: 1. the ctc2 and pwm2 bit definition names are now obsolete. use the wgm21:0 def- initions. however, the functionality and location of these bits are compatible with previous versions of the timer. bit 7 6 5 4 3 2 1 0 foc2a wgm20 com2a1 com2a0 wgm21 cs22 cs21 cs20 tccr2a read/write w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 table 61. waveform generation mode bit description (1) mode wgm21 (ctc2) wgm20 (pwm2) timer/counter mode of operation top update of ocr2a at tov2 flag set on 0 0 0 normal 0xff immediate max 1 0 1 pwm, phase correct 0xff top bottom 2 1 0 ctc ocr2a immediate max 3 1 1 fast pwm 0xff top max 136 atmega169v/l 2514j?avr?12/03 bit 5:4 ? com2a1:0: compare match output mode a these bits control the output compare pin (oc2a) behavior. if one or both of the com2a1:0 bits are set, the oc2a output overrides the normal port functionality of the i/o pin it is connected to. however, note that the data direction register (ddr) bit cor- responding to oc2a pin must be set in order to enable the output driver. when oc2a is connected to the pin, the function of the com2a1:0 bits depends on the wgm21:0 bit setting. table 62 shows the com2a1:0 bit functionality when the wgm21:0 bits are set to a normal or ctc mode (non-pwm). table 63 shows the com2a1:0 bit functionality when the wgm21:0 bits are set to fast pwm mode. note: 1. a special case occurs when ocr2a equals top and com2a1 is set. in this case, the compare match is ignored, but the set or clear is done at top. see ?fast pwm mode? on page 130 for more details. table 64 shows the com2a1:0 bit functionality when the wgm21:0 bits are set to phase correct pwm mode. note: 1. a special case occurs when ocr2a equals top and com2a1 is set. in this case, the compare match is ignored, but the set or clear is done at top. see ?phase cor- rect pwm mode? on page 131 for more details. table 62. compare output mode, non-pwm mode com2a1 com2a0 description 0 0 normal port operation, oc2a disconnected. 0 1 toggle oc2a on compare match. 1 0 clear oc2a on compare match. 1 1 set oc2a on compare match. table 63. compare output mode, fast pwm mode (1) com2a1 com2a0 description 0 0 normal port operation, oc2a disconnected. 01reserved 1 0 clear oc2a on compare match, set oc2a at top. 1 1 set oc2a on compare match, clear oc2a at top. table 64. compare output mode, phase correct pwm mode (1) com2a1 com2a0 description 0 0 normal port operation, oc2a disconnected. 01reserved 1 0 clear oc2a on compare match when up-counting. set oc2a on compare match when downcounting. 1 1 set oc2a on compare match when up-counting. clear oc2a on compare match when downcounting. 137 atmega169v/l 2514j?avr?12/03 bit 2:0 ? cs22:0: clock select the three clock select bits select the clock source to be used by the timer/counter, see table 65. timer/counter register ? tcnt2 the timer/counter register gives direct access, both for read and write operations, to the timer/counter unit 8-bit counter. writing to the tcnt2 register blocks (removes) the compare match on the following timer clock. modifying the counter (tcnt2) while the counter is running, introduces a risk of missing a compare match between tcnt2 and the ocr2a register. output compare register a ? ocr2a the output compare register a contains an 8-bit value that is continuously compared with the counter value (tcnt2). a match can be used to generate an output compare interrupt, or to generate a waveform output on the oc2a pin. table 65. clock select bit description cs22 cs21 cs20 description 0 0 0 no clock source (timer/counter stopped). 001clk t2s /(no prescaling) 010clk t2s /8 (from prescaler) 011clk t2s /32 (from prescaler) 100clk t2s /64 (from prescaler) 101clk t2s /128 (from prescaler) 110clk t 2 s /256 (from prescaler) 111clk t 2 s /1024 (from prescaler) bit 76543210 tcnt2[7:0] tcnt2 read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 ocr2a[7:0] ocr2a read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 138 atmega169v/l 2514j?avr?12/03 asynchronous operation of the timer/counter asynchronous status register ? assr bit 4 ? exclk: enable external clock input when exclk is written to one, and asynchronous clock is selected, the external clock input buffer is enabled and an external clock can be input on timer oscillator 1 (tosc1) pin instead of a 32 khz crystal. writing to exclk should be done before asynchronous operation is selected. note that the crystal oscillator will only run when this bit is zero. bit 3 ? as2: asynchronous timer/counter2 when as2 is written to zero, timer/counter2 is clocked from the i/o clock, clk i/o . when as2 is written to one, timer/counter2 is clocked from a crystal oscillator connected to the timer oscillator 1 (tosc1) pin. when the value of as2 is changed, the contents of tcnt2, ocr2a, and tccr2a might be corrupted. bit 2 ? tcn2ub: timer/counter2 update busy when timer/counter2 operates asynchronously and tcnt2 is written, this bit becomes set. when tcnt2 has been updated from the temporary storage register, this bit is cleared by hardware. a logical zero in this bit indicates that tcnt2 is ready to be updated with a new value. bit 1 ? ocr2ub: output compare register2 update busy when timer/counter2 operates asynchronously and ocr2a is written, this bit becomes set. when ocr2a has been updated from the temporary storage register, this bit is cleared by hardware. a logical zero in this bit indicates that ocr2a is ready to be updated with a new value. bit 0 ? tcr2ub: timer/counter control register2 update busy when timer/counter2 operates asynchronously and tccr2a is written, this bit becomes set. when tccr2a has been updated from the temporary storage register, this bit is cleared by hardware. a logical zero in this bit indicates that tccr2a is ready to be updated with a new value. if a write is performed to any of the three timer/counter2 registers while its update busy flag is set, the updated value might get corrupted and cause an unintentional inter- rupt to occur. the mechanisms for reading tcnt2, ocr2 a, and tccr2a are different. when read- ing tcnt2, the actual timer value is read. when reading ocr2a or tccr2a, the value in the temporary storage register is read. bit 7 6 5 4 3 2 1 0 ? ? ? exclk as2 tcn2ub ocr2ub tcr2ub assr read/write r r r r/w r/w r r r initial value 0 0 0 0 0 0 0 0 139 atmega169v/l 2514j?avr?12/03 asynchronous operation of timer/counter2 when timer/counter2 operates asynchronously, some considerations must be taken. warning: when switching between asynchronous and synchronous clocking of timer/counter2, the timer registers tcnt2, ocr2a, and tccr2a might be corrupted. a safe procedure for switching clock source is: 1. disable the timer/counter2 interrupts by clearing ocie2a and toie2. 2. select clock source by setting as2 as appropriate. 3. write new values to tcnt2, ocr2a, and tccr2a. 4. to switch to asynchronous operation: wait for tcn2ub, ocr2ub, and tcr2ub. 5. clear the timer/counter2 interrupt flags. 6. enable interrupts, if needed. the cpu main clock frequency must be more than four times the oscillator frequency. when writing to one of the registers tcnt2, ocr2a, or tccr2a, the value is transferred to a temporary register, and latched after two positive edges on tosc1. the user should not write a new value before the contents of the temporary register have been transferred to its destination. each of the three mentioned registers have their individual temporary register, which means that e.g. writing to tcnt2 does not disturb an ocr2a write in progress. to detect that a transfer to the destination register has taken place, the asynchronous status register ? assr has been implemented. when entering power-save or adc noise reduction mode after having written to tcnt2, ocr2a, or tccr2a, the user must wait until the written register has been updated if timer/counter2 is used to wake up the device. otherwise, the mcu will enter sleep mode before the changes are effective. this is particularly important if the output compare2 interrupt is used to wake up the device, since the output compare function is disabled during writing to ocr2a or tcnt2. if the write cycle is not finished, and the mcu enters sleep mode before the ocr2ub bit returns to zero, the device will never receive a compare match interrupt, and the mcu will not wake up. if timer/counter2 is used to wake the device up from power-save or adc noise reduction mode, precautions must be taken if the user wants to re-enter one of these modes: the interrupt logic needs one tosc1 cycle to be reset. if the time between wake-up and re-entering sleep mode is less than one tosc1 cycle, the interrupt will not occur, and the device will fail to wake up. if the user is in doubt whether the time before re-entering power-save or adc noise reduction mode is sufficient, the following algorithm can be used to ensure that one tosc1 cycle has elapsed: 1. write a value to tccr2a, tcnt2, or ocr2a. 2. wait until the corresponding update busy flag in assr returns to zero. 3. enter power-save or adc noise reduction mode. when the asynchronous operation is selected, the 32.768 khz oscillator for timer/counter2 is always running, except in power-down and standby modes. after a power-up reset or wake-up from power-down or standby mode, the user should be aware of the fact that this oscillator might take as long as one second to stabilize. the user is advised to wait for at least one second before using timer/counter2 after power-up or wake-up from power-down or standby mode. the contents of all timer/counter2 registers must be considered lost after a wake-up from power- down or standby mode due to unstable clock signal upon start-up, no matter whether the oscillator is in use or a clock signal is applied to the tosc1 pin. 140 atmega169v/l 2514j?avr?12/03 description of wake up from power-save or adc noise reduction mode when the timer is clocked asynchronously: when the interrupt condition is met, the wake up process is started on the following cycle of the timer clock, that is, the timer is always advanced by at least one before the processor can read the counter value. after wake-up, the mcu is halted for four cycles, it executes the interrupt routine, and resumes execution from the instruction following sleep. reading of the tcnt2 register shortly after wake-up from power-save may give an incorrect result. since tcnt2 is clocked on the asynchronous tosc clock, reading tcnt2 must be done through a register synchronized to the internal i/o clock domain. synchronization takes place for every rising tosc1 edge. when waking up from power-save mode, and the i/o clock (clk i/o ) again becomes active, tcnt2 will read as the previous value (before entering sleep) until the next rising tosc1 edge. the phase of the tosc clock after waking up from power-save mode is essentially unpredictable, as it depends on the wake-up time. the recommended procedure for reading tcnt2 is thus as follows: 1. write any value to either of the registers ocr2a or tccr2a. 2. wait for the corresponding update busy flag to be cleared. 3. read tcnt2. during asynchronous operation, the synchronization of the interrupt flags for the asynchronous timer takes 3 processor cycles plus one timer cycle. the timer is therefore advanced by at least one before the processor can read the timer value causing the setting of the interrupt flag. the output compare pin is changed on the timer clock and is not synchronized to the processor clock. timer/counter2 interrupt mask register ? timsk2 bit 1 ? ocie2a: timer/counter2 output compare match a interrupt enable when the ocie2a bit is written to one and the i-bit in the status register is set (one), the timer/counter2 compare match a interrupt is enabled. the corresponding interrupt is executed if a compare match in timer/counter2 occurs, i.e., when the ocf2a bit is set in the timer/counter 2 interrupt flag register ? tifr2. bit 0 ? toie2: timer/counter2 overflow interrupt enable when the toie2 bit is written to one and the i-bit in the status register is set (one), the timer/counter2 overflow interrupt is enabled. the corresponding interrupt is executed if an overflow in timer/counter2 occurs, i.e., when the tov2 bit is set in the timer/counter2 interrupt flag register ? tifr2. bit 76543210 ? ? ? ? ? ? ocie2a toie2 timsk2 read/write r r r r r r r/w r/w initial value 0 0 0 0 0 0 0 0 141 atmega169v/l 2514j?avr?12/03 timer/counter2 interrupt flag register ? tifr2 bit 1 ? ocf2a: output compare flag 2 a the ocf2a bit is set (one) when a compare match occurs between the timer/counter2 and the data in ocr2a ? output compare register2. ocf2a is cleared by hardware when executing the corresponding interrupt handling vector. alternatively, ocf2a is cleared by writing a logic one to the flag. when the i-bit in sreg, ocie2a (timer/counter2 compare match interrupt enable), and ocf2a are set (one), the timer/counter2 compare match interrupt is executed. bit 0 ? tov2: timer/counter2 overflow flag the tov2 bit is set (one) when an overflow occurs in timer/counter2. tov2 is cleared by hardware when executing the corresponding interrupt handling vector. alternatively, tov2 is cleared by writing a logic one to the flag. when the sreg i-bit, toie2a (timer/counter2 overflow interrupt enable), and tov2 are set (one), the timer/counter2 overflow interrupt is executed. in pwm mode, this bit is set when timer/counter2 changes counting direction at 0x00. bit 76543210 ? ? ? ? ? ? ocf2a tov2 tifr2 read/write r r r r r r r/w r/w initial value00000000 142 atmega169v/l 2514j?avr?12/03 timer/counter prescaler figure 63. prescaler for timer/counter2 the clock source for timer/counter2 is named clk t2s . clk t2s is by default connected to the main system i/o clock clk i o . by setting the as2 bit in assr, timer/counter2 is asyn- chronously clocked from the tosc1 pin. this enables use of timer/counter2 as a real time counter (rtc). when as2 is set, pins tosc1 and tosc2 are disconnected from port c. a crystal can then be connected between the tosc1 and tosc2 pins to serve as an independent clock source for timer/counter2. the oscillator is optimized for use with a 32.768 khz crystal. applying an external clock source to tosc1 is not recommended. for timer/counter2, the possible prescaled selections are: clk t2s /8, clk t2s /32, clk t2s /64, clk t2s /128, clk t2s /256, and clk t2s /1024. additionally, clk t2s as well as 0 (stop) may be selected. setting the psr2 bit in gtccr resets the prescaler. this allows the user to operate with a predictable prescaler. general timer/counter control register ? gtccr bit 1 ? psr2: prescaler reset timer/counter2 when this bit is one, the timer/counter2 prescaler will be reset. this bit is normally cleared immediately by hardware. if the bit is written when timer/counter2 is operating in asynchronous mode, the bit will remain one until the prescaler has been reset. the bit will not be cleared by hardware if the tsm bit is set. refer to the description of the ?bit 7 ? tsm: timer/counter synchronization mode? on page 94 for a description of the timer/counter synchronization mode. 10-bit t/c prescaler timer/counter2 clock source clk i/o clk t2s tosc1 as2 cs20 cs21 cs22 clk t2s /8 clk t2s /64 clk t2s /128 clk t2s /1024 clk t2s /256 clk t2s /32 0 psr2 clear clk t2 bit 7 6 5 4 3 2 1 0 tsm ? ? ? ? ? psr2 psr10 gtccr read/write r/w r r r r r r/w r/w initial value 0 0 0 0 0 0 0 0 143 atmega169v/l 2514j?avr?12/03 serial peripheral interface ? spi the serial peripheral interface (spi) allows high-speed synchronous data transfer between the atmega169 and peripheral devices or between several avr devices. the atmega169 spi includes the following features: full-duplex, three-wire synchronous data transfer master or slave operation lsb first or msb first data transfer seven programmable bit rates end of transmission interrupt flag write collision flag protection wake-up from idle mode double speed (ck/2) master spi mode figure 64. spi block diagram (1) note: 1. refer to figure 1 on page 2, and table 29 on page 60 for spi pin placement. the interconnection between master and slave cpus with spi is shown in figure 65. the system consists of two shift registers, and a master clock generator. the spi mas- ter initiates the communication cycle when pulling low the slave select ss pin of the desired slave. master and slave prepare the data to be sent in their respective shift registers, and the master generates the required clock pulses on the sck line to inter- change data. data is always shifted from master to slave on the master out ? slave in, mosi, line, and from slave to master on the master in ? slave out, miso, line. after each data packet, the master will synchronize the slave by pulling high the slave select, ss , line. spi2x spi2x divider /2/4/8/16/32/64/128 144 atmega169v/l 2514j?avr?12/03 when configured as a master, the spi interface has no automatic control of the ss line. this must be handled by user software before communication can start. when this is done, writing a byte to the spi data register starts the spi clock generator, and the hardware shifts the eight bits into the slave. after shifting one byte, the spi clock gener- ator stops, setting the end of transmission flag (spif). if the spi interrupt enable bit (spie) in the spcr register is set, an interrupt is requested. the master may continue to shift the next byte by writing it into spdr, or signal the end of packet by pulling high the slave select, ss line. the last incoming byte will be kept in the buffer register for later use. when configured as a slave, the spi interface will remain sleeping with miso tri-stated as long as the ss pin is driven high. in this state, software may update the contents of the spi data register, spdr, but the data will not be shifted out by incoming clock pulses on the sck pin until the ss pin is driven low. as one byte has been completely shifted, the end of transmission flag, spif is set. if the spi interrupt enable bit, spie, in the spcr register is set, an interrupt is requested. the slave may continue to place new data to be sent into spdr before reading the incoming data. the last incoming byte will be kept in the buffer register for later use. figure 65. spi master-slave interconnection the system is single buffered in the transmit direction and double buffered in the receive direction. this means that bytes to be transmitted cannot be written to the spi data register before the entire shift cycle is completed. when receiving data, however, a received character must be read from the spi data register before the next character has been completely shifted in. otherwise, the first byte is lost. in spi slave mode, the control logic will sample the incoming signal of the sck pin. to ensure correct sampling of the clock signal, the frequency of the spi clock should never exceed f osc /4. when the spi is enabled, the data direction of the mosi, miso, sck, and ss pins is overridden according to table 66. for more details on automatic port overrides, refer to ?alternate port functions? on page 56. note: 1. see ?alternate functions of port b? on page 60 for a detailed description of how to define the direction of the user defined spi pins. table 66. spi pin overrides (1) pin direction, master spi direction, slave spi mosi user defined input miso input user defined sck user defined input ss user defined input shift enable 145 atmega169v/l 2514j?avr?12/03 the following code examples show how to initialize the spi as a master and how to per- form a simple transmission. ddr_spi in the examples must be replaced by the actual data direction register controlling the spi pins. dd_mosi, dd_miso and dd_sck must be replaced by the actual data direction bits for these pins. e.g. if mosi is placed on pin pb5, replace dd_mosi with ddb5 and ddr_spi with ddrb. note: 1. the example code assumes that the part specific header file is included. assembly code example (1) spi_masterinit: ; set mosi and sck output, all others input ldi r17,(1< 148 atmega169v/l 2514j?avr?12/03 bit 4 ? mstr: master/slave select this bit selects master spi mode when written to one, and slave spi mode when written logic zero. if ss is configured as an input and is driven low while mstr is set, mstr will be cleared, and spif in spsr will become set. the user will then have to set mstr to re-enable spi master mode. bit 3 ? cpol: clock polarity when this bit is written to one, sck is high when idle. when cpol is written to zero, sck is low when idle. refer to figure 66 and figure 67 for an example. the cpol func- tionality is summarized below: bit 2 ? cpha: clock phase the settings of the clock phase bit (cpha) determine if data is sampled on the leading (first) or trailing (last) edge of sck. refer to figure 66 and figure 67 for an example. the cpol functionality is summarized below: bits 1, 0 ? spr1, spr0: spi clock rate select 1 and 0 these two bits control the sck rate of the device configured as a master. spr1 and spr0 have no effect on the slave. the relationship between sck and the oscillator clock frequency f osc is shown in the following table: table 67. cpol functionality cpol leading edge trailing edge 0 rising falling 1 falling rising table 68. cpha functionality cpha leading edge trailing edge 0 sample setup 1 setup sample table 69. relationship between sck and the oscillator frequency spi2x spr1 spr0 sck frequency 000 f osc / 4 001 f osc / 16 010 f osc / 64 011 f osc / 128 100 f osc / 2 101 f osc / 8 110 f osc / 32 111 f osc / 64 149 atmega169v/l 2514j?avr?12/03 spi status register ? spsr bit 7 ? spif: spi interrupt flag when a serial transfer is complete, the spif flag is set. an interrupt is generated if spie in spcr is set and global interrupts are enabled. if ss is an input and is driven low when the spi is in master mode, this will also set the spif flag. spif is cleared by hardware when executing the corresponding interrupt handling vector. alternatively, the spif bit is cleared by first reading the spi status register with spif set, then accessing the spi data register (spdr). bit 6 ? wcol: write collision flag the wcol bit is set if the spi data register (spdr) is written during a data transfer. the wcol bit (and the spif bit) are cleared by first reading the spi status register with wcol set, and then accessing the spi data register. bit 5..1 ? res: reserved bits these bits are reserved bits in the atmega169 and will always read as zero. bit 0 ? spi2x: double spi speed bit when this bit is written logic one the spi speed (sck frequency) will be doubled when the spi is in master mode (see table 69). this means that the minimum sck period will be two cpu clock periods. when the spi is configured as slave, the spi is only guaran- teed to work at f osc /4 or lower. the spi interface on the atmega169 is also used for program memory and eeprom downloading or uploading. see page 281 for serial programming and verification. spi data register ? spdr the spi data register is a read/write register used for data transfer between the regis- ter file and the spi shift register. writing to the register initiates data transmission. reading the register causes the shift register receive buffer to be read. bit 76543210 spif wcol ? ? ? ? ? spi2x spsr read/write r r r r r r r r/w initial value00000000 bit 76543210 msb lsb spdr read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value x x x x x x x x undefined 150 atmega169v/l 2514j?avr?12/03 data modes there are four combinations of sck phase and polarity with respect to serial data, which are determined by control bits cpha and cpol. the spi data transfer formats are shown in figure 66 and figure 67. data bits are shifted out and latched in on oppo- site edges of the sck signal, ensuring sufficient time for data signals to stabilize. this is clearly seen by summarizing table 67 and table 68, as done below: figure 66. spi transfer format with cpha = 0 figure 67. spi transfer format with cpha = 1 table 70. cpol functionality leading edge trailing edge spi mode cpol=0, cpha=0 sample (rising) setup (falling) 0 cpol=0, cpha=1 setup (rising) sample (falling) 1 cpol=1, cpha=0 sample (falling) setup (rising) 2 cpol=1, cpha=1 setup (falling) sample (rising) 3 bit 1 bit 6 lsb msb sck (cpol = 0) mode 0 sample i mosi/miso change 0 mosi pin change 0 miso pin sck (cpol = 1) mode 2 ss msb lsb bit 6 bit 1 bit 5 bit 2 bit 4 bit 3 bit 3 bit 4 bit 2 bit 5 msb first (dord = 0) lsb first (dord = 1) sck (cpol = 0) mode 1 sample i mosi/miso change 0 mosi pin change 0 miso pin sck (cpol = 1) mode 3 ss msb lsb bit 6 bit 1 bit 5 bit 2 bit 4 bit 3 bit 3 bit 4 bit 2 bit 5 bit 1 bit 6 lsb msb msb first (dord = 0) lsb first (dord = 1) 151 atmega169v/l 2514j?avr?12/03 usart the universal synchronous and asynchronous serial receiver and transmitter (usart) is a highly flexible serial communication device. the main features are: full duplex operation (independent serial receive and transmit registers) asynchronous or synchronous operation master or slave clocked synchronous operation high resolution baud rate generator supports serial frames with 5, 6, 7, 8, or 9 data bits and 1 or 2 stop bits odd or even parity generation and parity check supported by hardware data overrun detection framing error detection noise filtering includes false start bit detection and digital low pass filter three separate interrupts on tx complete, tx data register empty and rx complete multi-processor communication mode double speed asynchronous communication mode overview a simplified block diagram of the usart transmitter is shown in figure 68. cpu acces- sible i/o registers and i/o pins are shown in bold. figure 68. usart block diagram (1) note: 1. refer to figure 1 on page 2, table 36 on page 66, and table 30 on page 62 for usart pin placement. parity generator ubrr[h:l] udr (transmit) ucsra ucsrb ucsrc baud rate generator transmit shift register receive shift register rxd txd pin control udr (receive) pin control xck data recovery clock recovery pin control tx control rx control parity checker data bus osc sync logic clock generator transmitter receiver 152 atmega169v/l 2514j?avr?12/03 the dashed boxes in the block diagram separate the three main parts of the usart (listed from the top): clock generator, transmitter and receiver. control registers are shared by all units. the clock generation logic consists of synchronization logic for external clock input used by synchronous slave operation, and the baud rate generator. the xck (transfer clock) pin is only used by synchronous transfer mode. the trans- mitter consists of a single write buffer, a serial shift register, parity generator and control logic for handling different serial frame formats. the write buffer allows a contin- uous transfer of data without any delay between frames. the receiver is the most complex part of the usart module due to its clock and data recovery units. the recov- ery units are used for asynchronous data reception. in addition to the recovery units, the receiver includes a parity checker, control logic, a shift register and a two level receive buffer (udr). the receiver supports the same frame formats as the transmit- ter, and can detect frame error, data overrun and parity errors. avr usart vs. avr uart ? compatibility the usart is fully compatible with the avr uart regarding: bit locations inside all usart registers. baud rate generation. transmitter operation. transmit buffer functionality. receiver operation. however, the receive buffering has two improvements that will affect the compatibility in some special cases: a second buffer register has been added. the two buffer registers operate as a circular fifo buffer. therefore the udr must only be read once for each incoming data! more important is the fact that the error flags (fe and dor) and the ninth data bit (rxb8) are buffered with the data in the receive buffer. therefore the status bits must always be read before the udr register is read. otherwise the error status will be lost since the buffer state is lost. the receiver shift register can now act as a third buffer level. this is done by allowing the received data to remain in the serial shift register (see figure 68) if the buffer registers are full, until a new start bit is detected. the usart is therefore more resistant to data overrun (dor) error conditions. the following control bits have changed name, but have same functionality and register location: chr9 is changed to ucsz2. or is changed to dor. clock generation the clock generation logic generates the base clock for the transmitter and receiver. the usart supports four modes of clock operation: normal asynchronous, double speed asynchronous, master synchronous and slave synchronous mode. the umsel bit in usart control and status register c (ucsrc) selects between asynchronous and synchronous operation. double speed (asynchronous mode only) is controlled by the u2x found in the ucsra register. when using synchronous mode (umsel = 1), the data direction register for the xck pin (ddr_xck) controls whether the clock source is internal (master mode) or external (slave mode). the xck pin is only active when using synchronous mode. figure 69 shows a block diagram of the clock generation logic. 153 atmega169v/l 2514j?avr?12/03 figure 69. clock generation logic, block diagram signal description: txclk transmitter clock (internal signal). rxclk receiver base clock (internal signal). xcki input from xck pin (internal signal). used for synchronous slave operation. xcko clock output to xck pin (internal signal). used for synchronous master operation. fosc xtal pin frequency (system clock). internal clock generation ? the baud rate generator internal clock generation is used for the asynchronous and the synchronous master modes of operation. the description in this section refers to figure 69. the usart baud rate register (ubrr) and the down-counter connected to it function as a programmable prescaler or baud rate generator. the down-counter, running at sys- tem clock (f osc ), is loaded with the ubrr value each time the counter has counted down to zero or when the ubrrl register is written. a clock is generated each time the counter reaches zero. this clock is the baud rate generator clock output (= f osc /(ubrr+1)). the transmitter divides the baud rate generator clock output by 2, 8 or 16 depending on mode. the baud rate generator output is used directly by the receiver?s clock and data recovery units. however, the recovery units use a state machine that uses 2, 8 or 16 states depending on mode set by the state of the umsel, u2x and ddr_xck bits. table 71 contains equations for calculating the baud rate (in bits per second) and for calculating the ubrr value for each mode of operation using an internally generated clock source. prescaling down-counter /2 ubrr /4 /2 fosc ubrr+1 sync register osc xck pin txclk u2x umsel ddr_xck 0 1 0 1 xcki xcko ddr_xck rxclk 0 1 1 0 edge detector ucpol 154 atmega169v/l 2514j?avr?12/03 note: 1. the baud rate is defined to be the transfer rate in bit per second (bps) baud baud rate (in bits per second, bps) f osc system oscillator clock frequency ubrr contents of the ubrrh and ubrrl registers, (0-4095) some examples of ubrr values for some system clock frequencies are found in table 79 (see page 174). double speed operation (u2x) the transfer rate can be doubled by setting the u2x bit in ucsra. setting this bit only has effect for the asynchronous operation. set this bit to zero when using synchronous operation. setting this bit will reduce the divisor of the baud rate divider from 16 to 8, effectively doubling the transfer rate for asynchronous communication. note however that the receiver will in this case only use half the number of samples (reduced from 16 to 8) for data sampling and clock recovery, and therefore a more accurate baud rate setting and system clock are required when this mode is used. for the transmitter, there are no downsides. external clock external clocking is used by the synchronous slave modes of operation. the description in this section refers to figure 69 for details. external clock input from the xck pin is sampled by a synchronization register to mini- mize the chance of meta-stability. the output from the synchronization register must then pass through an edge detector before it can be used by the transmitter and receiver. this process introduces a two cpu clock period delay and therefore the max- imum external xck clock frequency is limited by the following equation: note that f osc depends on the stability of the system clock source. it is therefore recom- mended to add some margin to avoid possible loss of data due to frequency variations. table 71. equations for calculating baud rate register setting operating mode equation for calculating baud rate (1) equation for calculating ubrr value asynchronous normal mode (u2x = 0) asynchronous double speed mode (u2x = 1) synchronous master mode baud f osc 16 ubrr 1 + () -------------------------------------- - = ubrr f osc 16 baud ----------------------- - 1 ? = baud f osc 8 ubrr 1 + () ----------------------------------- = ubrr f osc 8 baud -------------------- 1 ? = baud f osc 2 ubrr 1 + () ----------------------------------- = ubrr f osc 2 baud -------------------- 1 ? = f xck f osc 4 ----------- < 155 atmega169v/l 2514j?avr?12/03 synchronous clock operation when synchronous mode is used (umsel = 1), the xck pin will be used as either clock input (slave) or clock output (master). the dependency between the clock edges and data sampling or data change is the same. the basic principle is that data input (on rxd) is sampled at the opposite xck clock edge of the edge the data output (txd) is changed. figure 70. synchronous mode xck timing. the ucpol bit ucrsc selects which xck clock edge is used for data sampling and which is used for data change. as figure 70 shows, when ucpol is zero the data will be changed at rising xck edge and sampled at falling xck edge. if ucpol is set, the data will be changed at fa lling xck edge and sampled at rising xck edge. frame formats a serial frame is defined to be one character of data bits with synchronization bits (start and stop bits), and optionally a parity bit for error checking. the usart accepts all 30 combinations of the following as valid frame formats: 1 start bit 5, 6, 7, 8, or 9 data bits no, even or odd parity bit 1 or 2 stop bits a frame starts with the start bit followed by the least significant data bit. then the next data bits, up to a total of nine, are succeeding, ending with the most significant bit. if enabled, the parity bit is inserted after the data bits, before the stop bits. when a com- plete frame is transmitted, it can be directly followed by a new frame, or the communication line can be set to an idle (high) state. figure 71 illustrates the possible combinations of the frame formats. bits inside brackets are optional. figure 71. frame formats st start bit, always low. (n) data bits (0 to 8). p parity bit. can be odd or even. rxd / txd xck rxd / txd xck ucpol = 0 ucpol = 1 sample sample 1 0 2 3 4 [5] [6] [7] [8] [p] st sp1 [sp2] (st / idle) (idle) frame 156 atmega169v/l 2514j?avr?12/03 sp stop bit, always high. idle no transfers on the communication line (rxd or txd). an idle line must be high. the frame format used by the usart is set by the ucsz2:0, upm1:0 and usbs bits in ucsrb and ucsrc. the receiver and transmitter use the same setting. note that changing the setting of any of these bits will corrupt all ongoing communication for both the receiver and transmitter. the usart character size (ucsz2:0) bits select the number of data bits in the frame. the usart parity mode (upm1:0) bits enable and set the type of parity bit. the selec- tion between one or two stop bits is done by the usart stop bit select (usbs) bit. the receiver ignores the second stop bit. an fe (frame error) will therefore only be detected in the cases where the first stop bit is zero. parity bit calculation the parity bit is calculated by doing an exclusive-or of all the data bits. if odd parity is used, the result of the exclusive or is inverted. the relation between the parity bit and data bits is as follows: p even parity bit using even parity p odd parity bit using odd parity d n data bit n of the character if used, the parity bit is located between the last data bit and first stop bit of a serial frame. usart initialization the usart has to be initialized before any communication can take place. the initial- ization process normally consists of setting the baud rate, setting frame format and enabling the transmitter or the receiver depending on the usage. for interrupt driven usart operation, the global interrupt flag should be cleared (and interrupts globally disabled) when doing the initialization. before doing a re-initialization with changed baud rate or frame format, be sure that there are no ongoing transmissions during the period the registers are changed. the txc flag can be used to check that the transmitter has completed all transfers, and the rxc flag can be used to check that there are no unread data in the receive buffer. note that the txc flag must be cleared before each transmission (before udr is written) if it is used for this purpose. p even d n 1 ? d 3 d 2 d 1 d 0 0 p odd d n 1 ? d 3 d 2 d 1 d 0 1 = = 157 atmega169v/l 2514j?avr?12/03 the following simple usart initialization code examples show one assembly and one c function that are equal in functionality. the examples assume asynchronous opera- tion using polling (no interrupts enabled) and a fixed frame format. the baud rate is given as a function parameter. for the assembly code, the baud rate parameter is assumed to be stored in the r17:r16 registers. note: 1. the example code assumes that the part specific header file is included. for i/o registers located in extended i/o ma p, ?in?, ?out?, ?sbis?, ?sbic?, ?cbi?, and ?sbi? instructions must be replaced with instructions that allow access to extended i/o. typically ?lds? and ?sts? combined with ?sbrs?, ?sbrc?, ?sbr?, and ?cbr?. more advanced initialization routines can be made that include frame format as parame- ters, disable interrupts and so on. however, many applications use a fixed setting of the baud and control registers, and for these types of applications the initialization code can be placed directly in the main routine, or be combined with initialization code for other i/o modules. assembly code example (1) usart_init: ; set baud rate out ubrrh, r17 out ubrrl, r16 ; enable receiver and transmitter ldi r16, (1< 161 atmega169v/l 2514j?avr?12/03 data reception ? the usart receiver the usart receiver is enabled by writing the receive enable (rxen) bit in the ucsrb register to one. when the receiver is enabled, the normal pin operation of the rxd pin is overridden by the usart and given the function as the receiver?s serial input. the baud rate, mode of operation and frame format must be set up once before any serial reception can be done. if synchronous operation is used, the clock on the xck pin will be used as transfer clock. receiving frames with 5 to 8 data bits the receiver starts data reception when it detects a valid start bit. each bit that follows the start bit will be sampled at the baud rate or xck clock, and shifted into the receive shift register until the first stop bit of a frame is received. a second stop bit will be ignored by the receiver. when the first stop bit is received, i.e., a complete serial frame is present in the receive shift register, the contents of the shift register will be moved into the receive buffer. the receive buffer can then be read by reading the udr i/o location. the following code example shows a simple usart receive function based on polling of the receive complete (rxc) flag. when using frames with less than eight bits the most significant bits of the data read from the udr will be masked to zero. the usart has to be initialized before the function can be used. note: 1. the example code assumes that the part specific header file is included. for i/o registers located in extended i/o ma p, ?in?, ?out?, ?sbis?, ?sbic?, ?cbi?, and ?sbi? instructions must be replaced with instructions that allow access to extended i/o. typically ?lds? and ?sts? combined with ?sbrs?, ?sbrc?, ?sbr?, and ?cbr?. the function simply waits for data to be present in the receive buffer by checking the rxc flag, before reading the buffer and returning the value. assembly code example (1) usart_receive: ; wait for data to be received sbis ucsra, rxc rjmp usart_receive ; get and return received data from buffer in r16, udr ret c code example (1) unsigned char usart_receive( void ) { /* wait for data to be received */ while ( !(ucsra & (1< 163 atmega169v/l 2514j?avr?12/03 extended i/o. typically ?lds? and ?sts? combined with ?sbrs?, ?sbrc?, ?sbr?, and ?cbr?. the receive function example reads all the i/o registers into the register file before any computation is done. this gives an optimal receive buffer utilization since the buffer location read will be free to accept new data as early as possible. receive compete flag and interrupt the usart receiver has one flag that indicates the receiver state. the receive complete (rxc) flag indicates if there are unread data present in the receive buffer. this flag is one when unread data exist in the receive buffer, and zero when the receive buffer is empty (i.e., does not contain any unread data). if the receiver is disabled (rxen = 0), the receive buffer will be flushed and consequently the rxc bit will become zero. when the receive complete interrupt enable (rxcie) in ucsrb is set, the usart receive complete interrupt will be executed as long as the rxc flag is set (provided that global interrupts are enabled). when interrupt-driven data reception is used, the receive complete routine must read the received data from udr in order to clear the rxc flag, otherwise a new interrupt will occur once the interrupt routine terminates. receiver error flags the usart receiver has three error flags: frame error (fe), data overrun (dor) and parity error (upe). all can be accessed by reading ucsra. common for the error flags is that they are located in the receive buffer together with the frame for which they indicate the error status. due to the buffering of the error flags, the ucsra must be read before the receive buffer (udr), since reading the udr i/o location changes the buffer read location. another equality for the error flags is that they can not be altered by software doing a write to the flag location. however, all flags must be set to zero when the ucsra is written for upward compatibility of future usart implementations. none of the error flags can generate interrupts. the frame error (fe) flag indicates the state of the first stop bit of the next readable frame stored in the receive buffer. the fe flag is zero when the stop bit was correctly read (as one), and the fe flag will be one when the stop bit was incorrect (zero). this flag can be used for detecting out-of-sync conditions, detecting break conditions and protocol handling. the fe flag is not affected by the setting of the usbs bit in ucsrc since the receiver ignores all, except for the first, stop bits. for compatibility with future devices, always set this bit to zero when writing to ucsra. the data overrun (dor) flag indicates data loss due to a receiver buffer full condition. a data overrun occurs when the receive buffer is full (two characters), it is a new char- acter waiting in the receive shift register, and a new start bit is detected. if the dor flag is set there was one or more serial frame lost between the frame last read from udr, and the next frame read from udr. for compatibility with future devices, always write this bit to zero when writing to ucsra. the dor flag is cleared when the frame received was successfully moved from the shift register to the receive buffer. the parity error (upe) flag indicates that the next frame in the receive buffer had a par- ity error when received. if parity check is not enabled the upe bit will always be read zero. for compatibility with future devices, always set this bit to zero when writing to ucsra. for more details see ?parity bit calculation? on page 156 and ?parity checker? on page 164. 164 atmega169v/l 2514j?avr?12/03 parity checker the parity checker is active when the high usart parity mode (upm1) bit is set. type of parity check to be performed (odd or even) is selected by the upm0 bit. when enabled, the parity checker calculates the parity of the data bits in incoming frames and compares the result with the parity bit from the serial frame. the result of the check is stored in the receive buffer together with the received data and stop bits. the parity error (upe) flag can then be read by software to check if the frame had a parity error. the upe bit is set if the next character that can be read from the receive buffer had a parity error when received and the parity checking was enabled at that point (upm1 = 1). this bit is valid until the receive buffer (udr) is read. disabling the receiver in contrast to the transmitter, disabling of the receiver will be immediate. data from ongoing receptions will therefore be lost. when disabled (i.e., the rxen is set to zero) the receiver will no longer override the normal function of the rxd port pin. the receiver buffer fifo will be flushed when the receiver is disabled. remaining data in the buffer will be lost flushing the receive buffer the receiver buffer fifo will be flushed when the receiver is disabled, i.e., the buffer will be emptied of its contents. unread data will be lost. if the buffer has to be flushed during normal operation, due to for instance an error condition, read the udr i/o loca- tion until the rxc flag is cleared. the following code example shows how to flush the receive buffer. note: 1. the example code assumes that the part specific header file is included. for i/o registers located in extended i/o ma p, ?in?, ?out?, ?sbis?, ?sbic?, ?cbi?, and ?sbi? instructions must be replaced with instructions that allow access to extended i/o. typically ?lds? and ?sts? combined with ?sbrs?, ?sbrc?, ?sbr?, and ?cbr?. asynchronous data reception the usart includes a clock recovery and a data recovery unit for handling asynchro- nous data reception. the clock recovery logic is used for synchronizing the internally generated baud rate clock to the incoming asynchronous serial frames at the rxd pin. the data recovery logic samples and low pass filters each incoming bit, thereby improv- ing the noise immunity of the receiver. the asynchronous reception operational range depends on the accuracy of the internal baud rate clock, the rate of the incoming frames, and the frame size in number of bits. assembly code example (1) usart_flush: sbis ucsra, rxc ret in r16, udr rjmp usart_flush c code example (1) void usart_flush( void ) { unsigned char dummy; while ( ucsra & (1< 166 atmega169v/l 2514j?avr?12/03 figure 74 shows the sampling of the stop bit and the earliest possible beginning of the start bit of the next frame. figure 74. stop bit sampling and next start bit sampling the same majority voting is done to the stop bit as done for the other bits in the frame. if the stop bit is registered to have a logic 0 value, the frame error (fe) flag will be set. a new high to low transition indicating the start bit of a new frame can come right after the last of the bits used for majority voting. for normal speed mode, the first low level sample can be at point marked (a) in figure 74. for double speed mode the first low level must be delayed to (b). (c) marks a stop bit of full length. the early start bit detec- tion influences the operational range of the receiver. asynchronous operational range the operational range of the receiver is dependent on the mismatch between the received bit rate and the internally generated baud rate. if the transmitter is sending frames at too fast or too slow bit rates, or the internally generated baud rate of the receiver does not have a similar (see table 72) base frequency, the receiver will not be able to synchronize the frames to the start bit. the following equations can be used to calculate the ratio of the incoming data rate and internal receiver baud rate. d sum of character size and parity size (d = 5 to 10 bit) s samples per bit. s = 16 for normal speed mode and s = 8 for double speed mode. s f first sample number used for majority voting. s f = 8 for normal speed and s f = 4 for double speed mode. s m middle sample number used for majority voting. s m = 9 for normal speed and s m = 5 for double speed mode. r slow is the ratio of the slowest incoming data rate that can be accepted in relation to the receiver baud rate. r fast is the ratio of the fastest incoming data rate that can be accepted in relation to the receiver baud rate. table 72 and table 73 list the maximum receiver baud rate error that can be tolerated. note that normal speed mode has higher toleration of baud rate variations. 1234567 8 9 10 0/1 0/1 0/1 stop 1 123 4 5 6 0/1 rxd sample (u2x = 0) sample (u2x = 1) (a) (b) (c) r slow d 1 + () s s 1 ? ds ? s f ++ ------------------------------------------ - = r fast d 2 + () s d 1 + () ss m + ----------------------------------- = 167 atmega169v/l 2514j?avr?12/03 the recommendations of the maximum receiver baud rate error was made under the assumption that the receiver and transmitter equally divides the maximum total error. there are two possible sources for the receivers baud rate error. the receiver?s system clock (xtal) will always have some minor instability over the supply voltage range and the temperature range. when using a crystal to generate the system clock, this is rarely a problem, but for a resonator the system clock may differ more than 2% depending of the resonators tolerance. the second source for the error is more controllable. the baud rate generator can not always do an exact division of the system frequency to get the baud rate wanted. in this case an ubrr value that gives an acceptable low error can be used if possible. table 72. recommended maximum receiver baud rate error for normal speed mode (u2x = 0) d # (data+parity bit) r slow (%) r fast (%) max total error (%) recommended max receiver error (%) 5 93.20 106.67 +6.67/-6.8 3.0 6 94.12 105.79 +5.79/-5.88 2.5 7 94.81 105.11 +5.11/-5.19 2.0 8 95.36 104.58 +4.58/-4.54 2.0 9 95.81 104.14 +4.14/-4.19 1.5 10 96.17 103.78 +3.78/-3.83 1.5 table 73. recommended maximum receiver baud rate error for double speed mode (u2x = 1) d # (data+parity bit) r slow (%) r fast (%) max total error (%) recommended max receiver error (%) 5 94.12 105.66 +5.66/-5.88 2.5 6 94.92 104.92 +4.92/-5.08 2.0 7 95.52 104,35 +4.35/-4.48 1.5 8 96.00 103.90 +3.90/-4.00 1.5 9 96.39 103.53 +3.53/-3.61 1.5 10 96.70 103.23 +3.23/-3.30 1.0 168 atmega169v/l 2514j?avr?12/03 multi-processor communication mode setting the multi-processor communication mode (mpcm) bit in ucsra enables a fil- tering function of incoming frames received by the usart receiver. frames that do not contain address information will be ignored and not put into the receive buffer. this effectively reduces the number of incoming frames that has to be handled by the cpu, in a system with multiple mcus that communicate via the same serial bus. the trans- mitter is unaffected by the mpcm setting, but has to be used differently when it is a part of a system utilizing the multi-processor communication mode. if the receiver is set up to receive frames that contain 5 to 8 data bits, then the first stop bit indicates if the frame contains data or address information. if the receiver is set up for frames with nine data bits, then the ninth bit (rxb8) is used for identifying address and data frames. when the frame type bit (the first stop or the ninth bit) is one, the frame contains an address. when the frame type bit is zero the frame is a data frame. the multi-processor communication mode enables several slave mcus to receive data from a master mcu. this is done by first decoding an address frame to find out which mcu has been addressed. if a particular slave mcu has been addressed, it will receive the following data frames as normal, while the other slave mcus will ignore the received frames until another address frame is received. using mpcm for an mcu to act as a master mcu, it can use a 9-bit character frame format (ucsz = 7). the ninth bit (txb8) must be set when an address frame (txb8 = 1) or cleared when a data frame (txb = 0) is being transmitted. the slave mcus must in this case be set to use a 9-bit character frame format. the following procedure should be used to exchange data in multi-processor communi- cation mode: 1. all slave mcus are in multi-processor communication mode (mpcm in ucsra is set). 2. the master mcu sends an address frame, and all slaves receive and read this frame. in the slave mcus, the rxc flag in ucsra will be set as normal. 3. each slave mcu reads the udr register and determines if it has been selected. if so, it clears the mpcm bit in ucsra, otherwise it waits for the next address byte and keeps the mpcm setting. 4. the addressed mcu will receive all data frames until a new address frame is received. the other slave mcus, which still have the mpcm bit set, will ignore the data frames. 5. when the last data frame is received by the addressed mcu, the addressed mcu sets the mpcm bit and waits for a new address frame from master. the process then repeats from 2. using any of the 5- to 8-bit character frame formats is possible, but impractical since the receiver must change between using n and n+1 character frame formats. this makes full-duplex operation difficult since the transmitter and receiver uses the same charac- ter size setting. if 5- to 8-bit character fr ames are used, the transmitter must be set to use two stop bit (usbs = 1) since the first stop bit is used for indicating the frame type. do not use read-modify-write instructions (sbi and cbi) to set or clear the mpcm bit. the mpcm bit shares the same i/o location as the txc flag and this might accidentally be cleared when using sbi or cbi instructions. 169 atmega169v/l 2514j?avr?12/03 usart register description usart i/o data register ? udr the usart transmit data buffer register and usart receive data buffer registers share the same i/o address referred to as usart data register or udr. the transmit data buffer register (txb) will be the destination for data written to the udr register location. reading the udr register location will return the contents of the receive data buffer register (rxb). for 5-, 6-, or 7-bit characters the upper u nused bits will be ignored by the transmitter and set to zero by the receiver. the transmit buffer can only be written when the udre flag in the ucsra register is set. data written to udr when the udre flag is not set, will be ignored by the usart transmitter. when data is written to the transmit buffer, and the transmitter is enabled, the transmitter will load the data into the transmit shift register when the shift register is empty. then the data will be serially transmitted on the txd pin. the receive buffer consists of a two level fifo. the fifo will change its state whenever the receive buffer is accessed. due to this behavior of the receive buffer, do not use read-modify-write instructions (sbi and cbi) on this location. be careful when using bit test instructions (sbic and sbis), since these also will change the state of the fifo. usart control and status register a ? ucsra bit 7 ? rxc: usart receive complete this flag bit is set when there are unread data in the receive buffer and cleared when the receive buffer is empty (i.e., does not contain any unread data). if the receiver is dis- abled, the receive buffer will be flushed and consequently the rxc bit will become zero. the rxc flag can be used to generate a receive complete interrupt (see description of the rxcie bit). bit 6 ? txc: usart transmit complete this flag bit is set when the entire frame in the transmit shift register has been shifted out and there are no new data currently present in the transmit buffer (udr). the txc flag bit is automatically cleared when a transmit complete interrupt is executed, or it can be cleared by writing a one to its bit location. the txc flag can generate a transmit complete interrupt (see description of the txcie bit). bit 76543210 rxb[7:0] udr (read) txb[7:0] udr (write) read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 rxc txc udre fe dor upe u2x mpcm ucsra read/write r r/w r r r r r/w r/w initial value00100000 170 atmega169v/l 2514j?avr?12/03 bit 5 ? udre: usart data register empty the udre flag indicates if the transmit buffer (udr) is ready to receive new data. if udre is one, the buffer is empty, and therefore ready to be written. the udre flag can generate a data register empty interrupt (see description of the udrie bit). udre is set after a reset to indicate that the transmitter is ready. bit 4 ? fe: frame error this bit is set if the next character in the receive buffer had a frame error when received. i.e., when the first stop bit of the next character in the receive buffer is zero. this bit is valid until the receive buffer (udr) is read. the fe bit is zero when the stop bit of received data is one. always set this bit to zero when writing to ucsra. bit 3 ? dor: data overrun this bit is set if a data overrun condition is detected. a data overrun occurs when the receive buffer is full (two characters), it is a new character waiting in the receive shift register, and a new start bit is detected. this bit is valid until the receive buffer (udr) is read. always set this bit to zero when writing to ucsra. bit 2 ? upe: usart parity error this bit is set if the next character in the receive buffer had a parity error when received and the parity checking was enabled at that point (upm1 = 1). this bit is valid until the receive buffer (udr) is read. always set this bit to zero when writing to ucsra. bit 1 ? u2x: double the usart transmission speed this bit only has effect for the asynchronous operation. write this bit to zero when using synchronous operation. writing this bit to one will reduce the divisor of the baud rate divider from 16 to 8 effec- tively doubling the transfer rate for asynchronous communication. bit 0 ? mpcm: multi-processor communication mode this bit enables the multi-processor communication mode. when the mpcm bit is writ- ten to one, all the incoming frames received by the usart receiver that do not contain address information will be ignored. the transmitter is unaffected by the mpcm setting. for more detailed information see ?multi-processor communication mode? on page 168. 171 atmega169v/l 2514j?avr?12/03 usart control and status register b ? ucsrb bit 7 ? rxcie: rx complete interrupt enable writing this bit to one enables interrupt on the rxc flag. a usart receive complete interrupt will be generated only if the rxcie bit is written to one, the global interrupt flag in sreg is written to one and the rxc bit in ucsra is set. bit 6 ? txcie: tx complete interrupt enable writing this bit to one enables interrupt on the txc flag. a usart transmit complete interrupt will be generated only if the txcie bit is written to one, the global interrupt flag in sreg is written to one and the txc bit in ucsra is set. bit 5 ? udrie: usart data register empty interrupt enable writing this bit to one enables interrupt on the udre flag. a data register empty inter- rupt will be generated only if the udrie bit is written to one, the global interrupt flag in sreg is written to one and the udre bit in ucsra is set. bit 4 ? rxen: receiver enable writing this bit to one enables the usart re ceiver. the receiver will override normal port operation for the rxd pin when enabled. disabling the receiver will flush the receive buffer invalidating the fe, dor, and upe flags. bit 3 ? txen: transmitter enable writing this bit to one enables the usart transmitter. the transmitter will override nor- mal port operation for the txd pin when enabled. the disabling of the transmitter (writing txen to zero) will not become effective until ongoing and pending transmis- sions are completed, i.e., when the transmit shift register and transmit buffer register do not contain data to be transmitted. when disabled, the transmitter will no longer override the txd port. bit 2 ? ucsz2: character size the ucsz2 bits combined with the ucsz1:0 bit in ucsrc sets the number of data bits (character size) in a frame the receiver and transmitter use. bit 1 ? rxb8: receive data bit 8 rxb8 is the ninth data bit of the received character when operating with serial frames with nine data bits. must be read before reading the low bits from udr. bit 0 ? txb8: transmit data bit 8 txb8 is the ninth data bit in the character to be transmitted when operating with serial frames with nine data bits. must be written before writing the low bits to udr. bit 76543210 rxcie txcie udrie rxen txen ucsz2 rxb8 txb8 ucsrb read/write r/w r/w r/w r/w r/w r/w r r/w initial value00000000 172 atmega169v/l 2514j?avr?12/03 usart control and status register c ? ucsrc bit 6 ? umsel: usart mode select this bit selects between asynchronous and synchronous mode of operation. bit 5:4 ? upm1:0: parity mode these bits enable and set type of parity generation and check. if enabled, the transmit- ter will automatically generate and send the parity of the transmitted data bits within each frame. the receiver will generate a parity value for the incoming data and com- pare it to the upm0 setting. if a mismatch is detected, the upe flag in ucsra will be set. bit 3 ? usbs: stop bit select this bit selects the number of stop bits to be inserted by the transmitter. the receiver ignores this setting. bit 76543210 ? umsel upm1 upm0 usbs ucsz1 ucsz0 ucpol ucsrc read/write r r/w r/w r/w r/w r/w r/w r/w initial value00000110 table 74. umsel bit settings umsel mode 0 asynchronous operation 1 synchronous operation table 75. upm bits settings upm1 upm0 parity mode 0 0 disabled 01reserved 1 0 enabled, even parity 1 1 enabled, odd parity table 76. usbs bit settings usbs stop bit(s) 01-bit 12-bit 173 atmega169v/l 2514j?avr?12/03 bit 2:1 ? ucsz1:0: character size the ucsz1:0 bits combined with the ucsz2 bit in ucsrb sets the number of data bits (character size) in a frame the receiver and transmitter use. bit 0 ? ucpol: clock polarity this bit is used for synchronous mode only. write this bit to zero when asynchronous mode is used. the ucpol bit sets the relationship between data output change and data input sample, and the synchronous clock (xck). usart baud rate registers ? ubrrl and ubrrh bit 15:12 ? reserved bits these bits are reserved for future use. for compatibility with future devices, these bit must be written to zero when ubrrh is written. bit 11:0 ? ubrr11:0: usart baud rate register this is a 12-bit register which contains the usart baud rate. the ubrrh contains the four most significant bits, and the ubrrl contains the eight least significant bits of the usart baud rate. ongoing transmissions by the transmitter and receiver will be cor- rupted if the baud rate is changed. writing ubrrl will trigger an immediate update of the baud rate prescaler. table 77. ucsz bits settings ucsz2 ucsz1 ucsz0 character size 0 0 0 5-bit 0 0 1 6-bit 0 1 0 7-bit 0 1 1 8-bit 100reserved 101reserved 110reserved 1 1 1 9-bit table 78. ucpol bit settings ucpol transmitted data changed (output of txd pin) received data sampled (input on rxd pin) 0 rising xck edge falling xck edge 1 falling xck edge rising xck edge bit 151413121110 9 8 ? ? ? ? ubrr[11:8] ubrrh ubrr[7:0] ubrrl 76543210 read/write r r r r r/w r/w r/w r/w r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 00000000 174 atmega169v/l 2514j?avr?12/03 examples of baud rate setting for standard crystal and resonator frequencies, the most commonly used baud rates for asynchronous operation can be generated by using the ubrr settings in table 79. ubrr values which yield an actual baud rate differing less than 0.5% from the target baud rate, are bold in the table. higher error ratings are acceptable, but the receiver will have less noise resistance when the error ratings are high, especially for large serial frames (see ?asynchronous operational range? on page 166). the error values are cal- culated using the following equation: error[%] baudrate closest match baudrate ------------------------------------------------------- - 1 ? ?? ?? 100% ? = table 79. examples of ubrr settings for commonly used oscillator frequencies baud rate (bps) f osc = 1.0000 mhz f osc = 1.8432 mhz f osc = 2.0000 mhz u2x = 0 u2x = 1 u2x = 0 u2x = 1 u2x = 0 u2x = 1 ubrr error ubrr error ubrr error ubrr error ubrr error ubrr error 2400 25 0.2% 51 0.2% 47 0.0% 95 0.0% 51 0.2% 103 0.2% 4800 12 0.2% 25 0.2% 23 0.0% 47 0.0% 25 0.2% 51 0.2% 9600 6 -7.0% 12 0.2% 11 0.0% 23 0.0% 12 0.2% 25 0.2% 14.4k 3 8.5% 8 -3.5% 7 0.0% 15 0.0% 8 -3.5% 16 2.1% 19.2k 2 8.5% 6 -7.0% 5 0.0% 11 0.0% 6 -7.0% 12 0.2% 28.8k 1 8.5% 3 8.5% 3 0.0% 7 0.0% 3 8.5% 8 -3.5% 38.4k 1 -18.6% 2 8.5% 2 0.0% 5 0.0% 2 8.5% 6 -7.0% 57.6k 0 8.5% 1 8.5% 1 0.0% 3 0.0% 1 8.5% 3 8.5% 76.8k ? ? 1 -18.6% 1 -25.0% 2 0.0% 1 -18.6% 2 8.5% 115.2k ? ? 0 8.5% 0 0.0% 1 0.0% 0 8.5% 1 8.5% 230.4k??????00.0%???? 250k??????????00.0% max. (1) 62.5 kbps 125 kbps 115.2 kbps 230.4 kbps 125 kbps 250 kbps 1. ubrr = 0, error = 0.0% 175 atmega169v/l 2514j?avr?12/03 table 80. examples of ubrr settings for commonly used oscillator frequencies (continued) baud rate (bps) f osc = 3.6864 mhz f osc = 4.0000 mhz f osc = 7.3728 mhz u2x = 0 u2x = 1 u2x = 0 u2x = 1 u2x = 0 u2x = 1 ubrr error ubrr error ubrr error ubrr error ubrr error ubrr error 2400 95 0.0% 191 0.0% 103 0.2% 207 0.2% 191 0.0% 383 0.0% 4800 47 0.0% 95 0.0% 51 0.2% 103 0.2% 95 0.0% 191 0.0% 9600 23 0.0% 47 0.0% 25 0.2% 51 0.2% 47 0.0% 95 0.0% 14.4k 15 0.0% 31 0.0% 16 2.1% 34 -0.8% 31 0.0% 63 0.0% 19.2k 11 0.0% 23 0.0% 12 0.2% 25 0.2% 23 0.0% 47 0.0% 28.8k 7 0.0% 15 0.0% 8 -3.5% 16 2.1% 15 0.0% 31 0.0% 38.4k 5 0.0% 11 0.0% 6 -7.0% 12 0.2% 11 0.0% 23 0.0% 57.6k 3 0.0% 7 0.0% 3 8.5% 8 -3.5% 7 0.0% 15 0.0% 76.8k 2 0.0% 5 0.0% 2 8.5% 6 -7.0% 5 0.0% 11 0.0% 115.2k 1 0.0% 3 0.0% 1 8.5% 3 8.5% 3 0.0% 7 0.0% 230.4k 0 0.0% 1 0.0% 0 8.5% 1 8.5% 1 0.0% 3 0.0% 250k 0 -7.8% 1 -7.8% 0 0.0% 1 0.0% 1 -7.8% 3 -7.8% 0.5m ? ? 0 -7.8% ? ? 0 0.0% 0 -7.8% 1 -7.8% 1m ??????????0-7.8% max. (1) 230.4 kbps 460.8 kbps 250 kbps 0.5 mbps 460.8 kbps 921.6 kbps 1. ubrr = 0, error = 0.0% 176 atmega169v/l 2514j?avr?12/03 table 81. examples of ubrr settings for commonly used oscillator frequencies (continued) baud rate (bps) f osc = 8.0000 mhz f osc = 11.0592 mhz f osc = 14.7456 mhz u2x = 0 u2x = 1 u2x = 0 u2x = 1 u2x = 0 u2x = 1 ubrr error ubrr error ubrr error ubrr error ubrr error ubrr error 2400 207 0.2% 416 -0.1% 287 0.0% 575 0.0% 383 0.0% 767 0.0% 4800 103 0.2% 207 0.2% 143 0.0% 287 0.0% 191 0.0% 383 0.0% 9600 51 0.2% 103 0.2% 71 0.0% 143 0.0% 95 0.0% 191 0.0% 14.4k 34 -0.8% 68 0.6% 47 0.0% 95 0.0% 63 0.0% 127 0.0% 19.2k 25 0.2% 51 0.2% 35 0.0% 71 0.0% 47 0.0% 95 0.0% 28.8k 16 2.1% 34 -0.8% 23 0.0% 47 0.0% 31 0.0% 63 0.0% 38.4k 12 0.2% 25 0.2% 17 0.0% 35 0.0% 23 0.0% 47 0.0% 57.6k 8 -3.5% 16 2.1% 11 0.0% 23 0.0% 15 0.0% 31 0.0% 76.8k 6 -7.0% 12 0.2% 8 0.0% 17 0.0% 11 0.0% 23 0.0% 115.2k 3 8.5% 8 -3.5% 5 0.0% 11 0.0% 7 0.0% 15 0.0% 230.4k 1 8.5% 3 8.5% 2 0.0% 5 0.0% 3 0.0% 7 0.0% 250k 1 0.0% 3 0.0% 2 -7.8% 5 -7.8% 3 -7.8% 6 5.3% 0.5m 0 0.0% 1 0.0% ? ? 2 -7.8% 1 -7.8% 3 -7.8% 1m ??00.0%????0-7.8%1-7.8% max. (1) 0.5 mbps 1 mbps 691.2 kbps 1.3824 mbps 921.6 kbps 1.8432 mbps 1. ubrr = 0, error = 0.0% 177 atmega169v/l 2514j?avr?12/03 table 82. examples of ubrr settings for commonly used oscillator frequencies (continued) baud rate (bps) f osc = 16.0000 mhz f osc = 18.4320 mhz f osc = 20.0000 mhz u2x = 0 u2x = 1 u2x = 0 u2x = 1 u2x = 0 u2x = 1 ubrr error ubrr error ubrr error ubrr error ubrr error ubrr error 2400 416 -0.1% 832 0.0% 479 0.0% 959 0.0% 520 0.0% 1041 0.0% 4800 207 0.2% 416 -0.1% 239 0.0% 479 0.0% 259 0.2% 520 0.0% 9600 103 0.2% 207 0.2% 119 0.0% 239 0.0% 129 0.2% 259 0.2% 14.4k 68 0.6% 138 -0.1% 79 0.0% 159 0.0% 86 -0.2% 173 -0.2% 19.2k 51 0.2% 103 0.2% 59 0.0% 119 0.0% 64 0.2% 129 0.2% 28.8k 34 -0.8% 68 0.6% 39 0.0% 79 0.0% 42 0.9% 86 -0.2% 38.4k 25 0.2% 51 0.2% 29 0.0% 59 0.0% 32 -1.4% 64 0.2% 57.6k 16 2.1% 34 -0.8% 19 0.0% 39 0.0% 21 -1.4% 42 0.9% 76.8k 12 0.2% 25 0.2% 14 0.0% 29 0.0% 15 1.7% 32 -1.4% 115.2k 8 -3.5% 16 2.1% 9 0.0% 19 0.0% 10 -1.4% 21 -1.4% 230.4k 3 8.5% 8 -3.5% 4 0.0% 9 0.0% 4 8.5% 10 -1.4% 250k 3 0.0% 7 0.0% 4 -7.8% 8 2.4% 4 0.0% 9 0.0% 0.5m 1 0.0% 3 0.0% ? ? 4 -7.8% ? ? 4 0.0% 1m 00.0%10.0%???????? max. (1) 1 mbps 2 mbps 1.152 mbps 2.304 mbps 1.25 mbps 2.5 mbps 1. ubrr = 0, error = 0.0% 178 atmega169v/l 2514j?avr?12/03 universal serial interface ? usi the universal serial interface, or usi, provides the basic hardware resources needed for serial communication. combined with a minimum of control software, the usi allows significantly higher transfer rates and uses less code space than solutions based on software only. interrupts are included to minimize the processor load. the main features of the usi are: two-wire synchronous data transfer (master or slave, f sclmax = f ck /16) three-wire synchronous data transfer (master or slave f sckmax = f ck /4) data received interrupt wakeup from idle mode in two-wire mode: wake-up from all sleep modes, including power-down mode two-wire start condition detector with interrupt capability overview a simplified block diagram of the usi is shown on figure 75. for the actual placement of i/o pins, refer to ?pinout atmega169? on page 2. cpu accessible i/o registers, includ- ing i/o bits and i/o pins, are shown in bold. the device-specific i/o register and bit locations are listed in the ?usi register descriptions? on page 184. figure 75. universal serial interface, block diagram the 8-bit shift register is directly accessible via the data bus and contains the incoming and outgoing data. the register has no buffering so the data must be read as quickly as possible to ensure that no data is lost. the most significant bit is connected to one of two output pins depending of the wire mode configuration. a transparent latch is inserted between the serial register output and output pin, which delays the change of data out- put to the opposite clock edge of the data input sampling. the serial input is always sampled from the data input (di) pin independent of the configuration. the 4-bit counter can be both read and written via the data bus, and can generate an overflow interrupt. both the serial register and the counter are clocked simultaneously by the same clock source. this allows the counter to count the number of bits received or transmitted and generate an interrupt when the transfer is complete. note that when an external clock source is selected the counter counts both clock edges. in this case the counter counts the number of edges, and not the number of bits. the clock can be selected from three different sources: the usck pin, timer/counter0 compare match or from software. data bus usipf usitc usiclk usics0 usics1 usioif usioie usidc usisif usiwm0 usiwm1 usisie bit7 two-wire clock control unit do (output only) di/sda (input/open drain) usck/scl (input/open drain) 4-bit counter usidr usisr dq le usicr clock hold tim0 comp bit0 [1] 3 0 1 2 3 0 1 2 0 1 2 179 atmega169v/l 2514j?avr?12/03 the two-wire clock control unit can generate an interrupt when a start condition is detected on the two-wire bus. it can also generate wait states by holding the clock pin low after a start condition is detected, or after the counter overflows. functional descriptions three-wire mode the usi three-wire mode is compliant to the serial peripheral interface (spi) mode 0 and 1, but does not have the slave select (ss) pin functionality. however, this feature can be implemented in software if necessary. pin names used by this mode are: di, do, and usck. figure 76. three-wire mode operation, simplified diagram figure 76 shows two usi units operating in three-wire mode, one as master and one as slave. the two shift registers are interconnected in such way that after eight usck clocks, the data in each register are interchanged. the same clock also increments the usi?s 4-bit counter. the counter overflow (interrupt) flag, or usioif, can therefore be used to determine when a transfer is completed. the clock is generated by the master device software by toggling the usck pin via the port register or by writing a one to the usitc bit in usicr. figure 77. three-wire mode, timing diagram slave master bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0 do di usck bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0 do di usck portxn msb msb 654321lsb 1 2 3 4 5 6 7 8 654321lsb usck usck do di d c b a e cycle ( reference ) 180 atmega169v/l 2514j?avr?12/03 the three-wire mode timing is shown in figure 77. at the top of the figure is a usck cycle reference. one bit is shifted into the usi shift register (usidr) for each of these cycles. the usck timing is shown for both external clock modes. in external clock mode 0 (usics0 = 0), di is sampled at positive edges, and do is changed (data regis- ter is shifted by one) at negative edges. external clock mode 1 (usics0 = 1) uses the opposite edges versus mode 0, i.e., samples data at negative and changes the output at positive edges. the usi clock modes corresponds to the spi data mode 0 and 1. referring to the timing diagram (figure 77.), a bus transfer involves the following steps: 1. the slave device and master device sets up its data output and, depending on the protocol used, enables its output driver (mark a and b). the output is set up by writing the data to be transmitted to the serial data register. enabling of the output is done by setting the corresponding bit in the port data direction regis- ter. note that point a and b does not have any specific order, but both must be at least one half usck cycle before point c where the data is sampled. this must be done to ensure that the data setup requirement is satisfied. the 4-bit counter is reset to zero. 2. the master generates a clock pulse by software toggling the usck line twice (c and d). the bit value on the slave and master?s data input (di) pin is sampled by the usi on the first edge (c), and the data output is changed on the opposite edge (d). the 4-bit counter will count both edges. 3. step 2. is repeated eight times for a complete register (byte) transfer. 4. after eight clock pulses (i.e., 16 clock edges) the counter will overflow and indi- cate that the transfer is completed. the data bytes transferred must now be processed before a new transfer can be initiated. the overflow interrupt will wake up the processor if it is set to idle mode. depending of the protocol used the slave device can now set its output to high impedance. spi master operation example the following code demonstrates how to use the usi module as a spi master: spitransfer: sts usidr,r16 ldi r16,(1< 183 atmega169v/l 2514j?avr?12/03 figure 79. two-wire mode, typical timing diagram referring to the timing diagram (figure 79.), a bus transfer involves the following steps: 1. the a start condition is generated by the master by forcing the sda low line while the scl line is high (a). sda can be forced low either by writing a zero to bit 7 of the shift register, or by setting the corresponding bit in the port register to zero. note that the data direction register bit must be set to one for the output to be enabled. the slave device?s start detector logic (figure 80.) detects the start condition and sets the usisif flag. the flag can generate an interrupt if necessary. 2. in addition, the start detector will hold the scl line low after the master has forced an negative edge on this line (b). this allows the slave to wake up from sleep or complete its other tasks before setting up the shift register to receive the address. this is done by clearing the start condition flag and reset the counter. 3. the master set the first bit to be transferred and releases the scl line (c). the slave samples the data and shift it into the serial register at the positive edge of the scl clock. 4. after eight bits are transferred containing slave address and data direction (read or write), the slave counter overflows and the scl line is forced low (d). if the slave is not the one the master has addressed, it releases the scl line and waits for a new start condition. 5. if the slave is addressed it holds the sda line low during the acknowledgment cycle before holding the scl line low again (i.e., the counter register must be set to 14 before releasing scl at (d)). depending of the r/w bit the master or slave enables its output. if the bit is set, a master read operation is in progress (i.e., the slave drives the sda line) the slave can hold the scl line low after the acknowledge (e). 6. multiple bytes can now be transmitted, all in same direction, until a stop condition is given by the master (f). or a new start condition is given. if the slave is not able to receive more data it does not acknowledge the data byte it has last received. when the master does a read operation it must terminate the operation by force the acknowledge bit low after the last byte transmitted. figure 80. start condition detector, logic diagram p s address 1 - 7 8 9 r/w ack ack 1 - 8 9 data ack 1 - 8 9 data sda scl a b d e c f sda scl write( usisif) clock hold usisif dq clr dq clr 184 atmega169v/l 2514j?avr?12/03 start condition detector the start condition detector is shown in figure 80. the sda line is delayed (in the range of 50 to 300 ns) to ensure valid sampling of the scl line. the start condition detector is only enabled in two-wire mode. the start condition detector is working asynchronously and can therefore wake up the processor from the power-down sleep mode. however, the protocol used might have restrictions on the scl hold time. therefore, when using this feature in this case the oscillator start-up time set by the cksel fuses (see ?clock systems and their distribu- tion? on page 23) must also be taken into the consideration. refer to the usisif bit description on page 185 for further details. alternative usi usage when the usi unit is not used for serial communication, it can be set up to do alternative tasks due to its flexible design. half-duplex asynchronous data transfer by utilizing the shift register in three-wire mode, it is possible to implement a more compact and higher performance uart than by software only. 4-bit counter the 4-bit counter can be used as a stand-alone counter with overflow interrupt. note that if the counter is clocked externally, both clock edges will generate an increment. 12-bit timer/counter combining the usi 4-bit counter and timer/counter0 allows them to be used as a 12-bit counter. edge triggered external interrupt by setting the counter to maximum value (f) it can function as an additional external interrupt. the overflow flag and interrupt enable bit are then used for the external inter- rupt. this feature is selected by the usics1 bit. software interrupt the counter overflow interrupt can be used as a software interrupt triggered by a clock strobe. usi register descriptions usi data register ? usidr the usi uses no buffering of the serial register, i.e., when accessing the data register (usidr) the serial register is accessed directly. if a serial clock occurs at the same cycle the register is written, the register will contain the value written and no shift is per- formed. a (left) shift operation is performed depending of the usics1..0 bits setting. the shift operation can be controlled by an external clock edge, by a timer/counter0 com- pare match, or directly by software using the usiclk strobe bit. note that even when no wire mode is selected (usiwm1..0 = 0) both the external data input (di/sda) and the external clock input (usck/scl) can still be used by the shift register. the output pin in use, do or sda depending on the wire mode, is connected via the out- put latch to the most significant bit (bit 7) of the data register. the output latch is open (transparent) during the first half of a serial clock cycle when an external clock source is selected (usics1 = 1), and constantly open when an internal clock source is used (usics1 = 0). the output will be changed immediately when a new msb written as long as the latch is open. the latch ensures that data input is sampled and data output is changed on opposite clock edges. bit 7 6 5 4 3 2 1 0 msb lsb usidr read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 185 atmega169v/l 2514j?avr?12/03 note that the corresponding data direction register to the pin must be set to one for enabling data output from the shift register. usi status register ? usisr the status register contains interrupt flags, line status flags and the counter value. bit 7 ? usisif: start condition interrupt flag when two-wire mode is selected, the usisif flag is set (to one) when a start condition is detected. when output disable mode or three-wire mode is selected and (usicsx = 0b11 & usiclk = 0) or (usics = 0b10 & usiclk = 0), any edge on the sck pin sets the flag. an interrupt will be generated when the flag is set while the usisie bit in usicr and the global interrupt enable flag are set. the flag will only be cleared by writing a logical one to the usisif bit. clearing this bit will release the start detection hold of uscl in two- wire mode. a start condition interrupt will wakeup the processor from all sleep modes. bit 6 ? usioif: counter overflow interrupt flag this flag is set (one) when the 4-bit counter overflows (i.e., at the transition from 15 to 0). an interrupt will be generated when the flag is set while the usioie bit in usicr and the global interrupt enable flag are set. the flag will only be cleared if a one is written to the usioif bit. clearing this bit will release the counter overflow hold of scl in two- wire mode. a counter overflow interrupt will wakeup the processor from idle sleep mode. bit 5 ? usipf: stop condition flag when two-wire mode is selected, the usipf flag is set (one) when a stop condition is detected. the flag is cleared by writing a one to this bit. note that this is not an interrupt flag. this signal is useful when implementing two-wire bus master arbitration. bit 4 ? usidc: data output collision this bit is logical one when bit 7 in the shift register differs from the physical pin value. the flag is only valid when two-wire mode is used. this signal is useful when imple- menting two-wire bus master arbitration. bits 3..0 ? usicnt3..0: counter value these bits reflect the current 4-bit counter value. the 4-bit counter value can directly be read or written by the cpu. the 4-bit counter increments by one for each clock generated either by the external clock edge detector, by a timer/counter0 compare match, or by software using usi- clk or usitc strobe bits. the clock source depends of the setting of the usics1..0 bits. for external clock operation a special feature is added that allows the clock to be generated by writing to the usitc strobe bit. this feature is enabled by write a one to the usiclk bit while setting an external clock source (usics1 = 1). bit 76543 210 usisif usioif usipf usidc usicnt3 usicnt2 usicnt1 usicnt0 usisr read/write r/w r/w r/w r r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 186 atmega169v/l 2514j?avr?12/03 note that even when no wire mode is selected (usiwm1..0 = 0) the external clock input (usck/scl) are can still be used by the counter. usi control register ? usicr the control register includes interrupt enable control, wire mode setting, clock select setting, and clock strobe. bit 7 ? usisie: start condition interrupt enable setting this bit to one enables the start condition detector interrupt. if there is a pending interrupt when the usisie and the global interrupt enable flag is set to one, this will immediately be executed. refer to the usisif bit description on page 185 for further details. bit 6 ? usioie: counter overflow interrupt enable setting this bit to one enables the counter overflow interrupt. if there is a pending inter- rupt when the usioie and the global interrupt enable flag is set to one, this will immediately be executed. refer to the usioif bit description on page 185 for further details. bit 5..4 ? usiwm1..0: wire mode these bits set the type of wire mode to be used. basically only the function of the outputs are affected by these bits. data and clock inputs are not affected by the mode selected and will always have the same function. the counter and shift register can therefore be clocked externally, and data input sampled, even when outputs are disabled. the relations between usiwm1..0 and the usi operation is summarized in table 83. bit 7 6 5 4 3 2 1 0 usisie usioie usiwm1 usiwm0 usics1 usics0 usiclk usitc usicr read/write r/w r/w r/w r/w r/w r/w w w initial value 0 0 0 0 0 0 0 0 187 atmega169v/l 2514j?avr?12/03 note: 1. the di and usck pins are renamed to serial data (sda) and serial clock (scl) respectively to avoid confusion between the modes of operation. table 83. relations between usiwm1..0 and the usi operation usiwm1 usiwm0 description 0 0 outputs, clock hold, and start detector disabled. port pins operates as normal. 0 1 three-wire mode. uses do, di, and usck pins. the data output (do) pin overrides the corresponding bit in the port register in this mode. however, the corresponding ddr bit still controls the data direction. when the port pin is set as input the pins pull-up is controlled by the port bit. the data input (di) and serial clock (usck) pins do not affect the normal port operation. when operating as master, clock pulses are software generated by toggling the port register, while the data direction is set to output. the usitc bit in the usicr register can be used for this purpose. 1 0 two-wire mode. uses sda (di) and scl (usck) pins (1) . the serial data (sda) and the serial clock (scl) pins are bi- directional and uses open-collector output drives. the output drivers are enabled by setting the corresponding bit for sda and scl in the ddr register. when the output driver is enabled for the sda pin, the output driver will force the line sda low if the output of the shift register or the corresponding bit in the port register is zero. otherwise the sda line will not be driven (i.e., it is released). when the scl pin output driver is enabled the scl line will be forced low if the corresponding bit in the port register is zero, or by the start detector. otherwise the scl line will not be driven. the scl line is held low when a start detector detects a start condition and the output is enabled. clearing the start condition flag (usisif) releases the line. the sda and scl pin inputs is not affected by enabling this mode. pull-ups on the sda and scl port pin are disabled in two-wire mode. 1 1 two-wire mode. uses sda and scl pins. same operation as for the two-wire mode described above, except that the scl line is also held low when a counter overflow occurs, and is held low until the counter overflow flag (usioif) is cleared. 188 atmega169v/l 2514j?avr?12/03 bit 3..2 ? usics1..0: clock source select these bits set the clock source for the shift register and counter. the data output latch ensures that the output is changed at the opposite edge of the sampling of the data input (di/sda) when using external clock source (usck/scl). when software strobe or timer/counter0 compare match clock option is selected, the output latch is transparent and therefore the output is changed immediately. clearing the usics1..0 bits enables software strobe option. when using this option, writing a one to the usiclk bit clocks both the shift register and the counter. for external clock source (usics1 = 1), the usiclk bit is no longer used as a strobe, but selects between external clocking and software clocking by the usitc strobe bit. table 84 shows the relationship between the usics1..0 and usiclk setting and clock source used for the shift register and the 4-bit counter. bit 1 ? usiclk: clock strobe writing a one to this bit location strobes the shift register to shift one step and the counter to increment by one, provided that the usics1..0 bits are set to zero and by doing so the software clock strobe option is selected. the output will change immedi- ately when the clock strobe is executed, i.e., in the same instruction cycle. the value shifted into the shift register is sampled the previous instruction cycle. the bit will be read as zero. when an external clock source is selected (usics1 = 1), the usiclk function is changed from a clock strobe to a clock select register. setting the usiclk bit in this case will select the usitc strobe bit as clock source for the 4-bit counter (see table 84). bit 0 ? usitc: toggle clock port pin writing a one to this bit location toggles the usck/scl value either from 0 to 1, or from 1 to 0. the toggling is independent of the setting in the data direction register, but if the port value is to be shown on the pin the ddre4 must be set as output (to one). this feature allows easy clock generation when implementing master devices. the bit will be read as zero. when an external clock source is selected (usics1 = 1) and the usiclk bit is set to one, writing to the usitc strobe bit will directly clock the 4-bit counter. this allows an early detection of when the transfer is done when operating as a master device. table 84. relations between the usics1..0 and usiclk setting usics1 usics0 usiclk shift register clock source 4-bit counter clock source 0 0 0 no clock no clock 0 0 1 software clock strobe (usiclk) software clock strobe (usiclk) 0 1 x timer/counter0 compare match timer/counter0 compare match 1 0 0 external, positive edge external, both edges 1 1 0 external, negative edge external, both edges 1 0 1 external, positive edge software clock strobe (usitc) 1 1 1 external, negative edge software clock strobe (usitc) 189 atmega169v/l 2514j?avr?12/03 analog comparator the analog comparator compares the input values on the positive pin ain0 and nega- tive pin ain1. when the voltage on the positive pin ain0 is higher than the voltage on the negative pin ain1, the analog comparator output, aco, is set. the comparator?s output can be set to trigger the timer/counter1 input capture function. in addition, the comparator can trigger a separate interrupt, exclusive to the analog comparator. the user can select interrupt triggering on comparator output rise, fall or toggle. a block dia- gram of the comparator and its surrounding logic is shown in figure 81 . figure 81. analog comparator block diagram (2) notes: 1. see table 86 on page 191. 2. refer to figure 1 on page 2 and table 28 on page 60 for analog comparator pin placement. adc control and status register b ? adcsrb bit 6 ? acme: analog comparator multiplexer enable when this bit is written logic one and the adc is switched off (aden in adcsra is zero), the adc multiplexer selects the negative input to the analog comparator. when this bit is written logic zero, ain1 is applied to the negative input of the analog compar- ator. for a detailed description of this bit, see ?analog comparator multiplexed input? on page 191. analog comparator control and status register ? acsr bit 7 ? acd: analog comparator disable when this bit is written logic one, the power to the analog comparator is switched off. this bit can be set at any time to turn off the analog comparator. this will reduce power consumption in active and idle mode. when changing the acd bit, the analog compar- ator interrupt must be disabled by clearing the acie bit in acsr. otherwise an interrupt can occur when the bit is changed. acbg bandgap reference adc multiplexer output acme aden (1) bit 7 6543210 ? acme ? ? ? adts2 adts1 adts0 adcsrb read/write r r/w r r r r/w r/w r/w initial value0 0000000 bit 76543210 acd acbg aco aci acie acic acis1 acis0 acsr read/write r/w r/w r r/w r/w r/w r/w r/w initial value 0 0 n/a 0 0 0 0 0 190 atmega169v/l 2514j?avr?12/03 bit 6 ? acbg: analog comparator bandgap select when this bit is set, a fixed bandgap reference voltage replaces the positive input to the analog comparator. when this bit is cleared, ain0 is applied to the positive input of the analog comparator. see ?internal voltage reference? on page 41. bit 5 ? aco: analog comparator output the output of the analog comparator is synchronized and then directly connected to aco. the synchronization introduces a delay of 1 - 2 clock cycles. bit 4 ? aci: analog comparator interrupt flag this bit is set by hardware when a comparator output event triggers the interrupt mode defined by acis1 and acis0. the analog comparator interrupt routine is executed if the acie bit is set and the i-bit in sreg is set. aci is cleared by hardware when execut- ing the corresponding interrupt handling vector. alternatively, aci is cleared by writing a logic one to the flag. bit 3 ? acie: analog comparator interrupt enable when the acie bit is written logic one and the i-bit in the status register is set, the ana- log comparator interrupt is activated. when written logic zero, the interrupt is disabled. bit 2 ? acic: analog comparator input capture enable when written logic one, this bit enables the input capture function in timer/counter1 to be triggered by the analog comparator. the comparator output is in this case directly connected to the input capture front-end logic, making the comparator utilize the noise canceler and edge select features of the timer/counter1 input capture interrupt. when written logic zero, no connection between the analog comparator and the input capture function exists. to make the comparator trigger the timer/counter1 input capture inter- rupt, the icie1 bit in the timer interrupt mask register (timsk1) must be set. bits 1, 0 ? acis1, acis0: analog comparator interrupt mode select these bits determine which comparator events that trigger the analog comparator inter- rupt. the different settings are shown in table 85. when changing the acis1/acis0 bits, the analog comparator interrupt must be dis- abled by clearing its interrupt enable bit in the acsr register. otherwise an interrupt can occur when the bits are changed. table 85. acis1/acis0 settings acis1 acis0 interrupt mode 0 0 comparator interrupt on output toggle. 01reserved 1 0 comparator interrupt on falling output edge. 1 1 comparator interrupt on rising output edge. 191 atmega169v/l 2514j?avr?12/03 analog comparator multiplexed input it is possible to select any of the adc7..0 pins to replace the negative input to the ana- log comparator. the adc multiplexer is used to select this input, and consequently, the adc must be switched off to utilize this feature. if the analog comparator multiplexer enable bit (acme in adcsrb) is set and the adc is switched off (aden in adcsra is zero), mux2..0 in admux select the input pin to replace the negative input to the ana- log comparator, as shown in table 86. if acme is cleared or aden is set, ain1 is applied to the negative input to the analog comparator. digital input disable register 1 ? didr1 bit 1, 0 ? ain1d, ain0d: ain1, ain0 digital input disable when this bit is written logic one, the digital input buffer on the ain1/0 pin is disabled. the corresponding pin register bit will always read as zero when this bit is set. when an analog signal is applied to the ain1/0 pin and the digital input from this pin is not needed, this bit should be written logic one to reduce power consumption in the digital input buffer. table 86. analog comparator multiplexed input acme aden mux2..0 analog comparator negative input 0 x xxx ain1 1 1 xxx ain1 1 0 000 adc0 1 0 001 adc1 1 0 010 adc2 1 0 011 adc3 1 0 100 adc4 1 0 101 adc5 1 0 110 adc6 1 0 111 adc7 bit 76543210 ? ? ? ? ? ? ain1d ain0d didr1 read/write r r r r r r r/w r/w initial value00000000 192 atmega169v/l 2514j?avr?12/03 analog to digital converter features 10-bit resolution 0.5 lsb integral non-linearity 2 lsb absolute accuracy 13 s - 260 s conversion time (50 khz to 1 mhz adc clock) up to 15 ksps at maximum resolution (200 khz adc clock) eight multiplexed single ended input channels optional left adjustment for adc result readout 0 - v cc adc input voltage range selectable 1.1v adc reference voltage free running or single conversion mode adc start conversion by auto triggering on interrupt sources interrupt on adc conversion complete sleep mode noise canceler the atmega169 features a 10-bit successive approximation adc. the adc is con- nected to an 8-channel analog multiplexer which allows eight single-ended voltage inputs constructed from the pins of port a. the single-ended voltage inputs refer to 0v (gnd). the adc contains a sample and hold circuit which ensures that the input voltage to the adc is held at a constant level during conversion. a block diagram of the adc is shown in figure 82. the adc has a separate analog supply voltage pin, avcc. avcc must not differ more than 0.3v from v cc . see the paragraph ?adc noise canceler? on page 199 on how to connect this pin. internal reference voltages of nominally 1. 1v or avcc are provided on-chip. the volt- age reference may be externally decoupled at the aref pin by a capacitor for better noise performance. 193 atmega169v/l 2514j?avr?12/03 figure 82. analog to digital converter block schematic operation the adc converts an analog input voltage to a 10-bit digital value through successive approximation. the minimum value represents gnd and the maximum value represents the voltage on the aref pin minus 1 lsb. optionally, avcc or an internal 1.1v refer- ence voltage may be connected to the aref pin by writing to the refsn bits in the admux register. the internal voltage reference may thus be decoupled by an external capacitor at the aref pin to improve noise immunity. the analog input channel is selected by writing to the mux bits in admux. any of the adc input pins, as well as gnd and a fixed bandgap voltage reference, can be selected as single ended inputs to the adc. the adc is enabled by setting the adc enable bit, aden in adcsra. voltage reference and input channel selections will not go into effect until aden is set. the adc does not consume power when aden is cleared, so it is recommended to switch off the adc before entering power saving sleep modes. the adc generates a 10-bit result which is presented in the adc data registers, adch and adcl. by default, the result is presented right adjusted, but can optionally be presented left adjusted by setting the adlar bit in admux. if the result is left adjusted and no more than 8-bit precision is required, it is sufficient to read adch. otherwise, adcl must be read first, then adch, to ensure that the content of the data registers belongs to the same conversion. once adcl is read, adc access adc conversion complete irq 8-bit data bus 15 0 adc multiplexer select (admux) adc ctrl. & status register (adcsra) adc data register (adch/adcl) mux2 adie adate adsc aden adif adif mux1 mux0 adps0 adps1 adps2 mux3 conversion logic 10-bit dac + - sample & hold comparator internal reference mux decoder mux4 avcc adc7 adc6 adc5 adc4 adc3 adc2 adc1 adc0 refs0 refs1 adlar + - channel selection gain selection adc[9:0] adc multiplexer output differential amplifier aref bandgap reference prescaler single ended / differential selection gnd pos. input mux neg. input mux trigger select adts[2:0] interrupt flags start 194 atmega169v/l 2514j?avr?12/03 to data registers is blocked. this means that if adcl has been read, and a conversion completes before adch is read, neither register is updated and the result from the con- version is lost. when adch is read, adc access to the adch and adcl registers is re-enabled. the adc has its own interrupt which can be triggered when a conversion completes. when adc access to the data registers is prohibited between reading of adch and adcl, the interrupt will trigger even if the result is lost. starting a conversion a single conversion is started by writing a logical one to the adc start conversion bit, adsc. this bit stays high as long as the conversion is in progress and will be cleared by hardware when the conversion is completed. if a different data channel is selected while a conversion is in progress, the adc will finish the current conversion before performing the channel change. alternatively, a conversion can be triggered automatically by various sources. auto trig- gering is enabled by setting the adc auto trigger enable bit, adate in adcsra. the trigger source is selected by setting the adc trigger select bits, adts in adcsrb (see description of the adts bits for a list of the trigger sources). when a positive edge occurs on the selected trigger signal, the adc prescaler is reset and a conversion is started. this provides a method of starting conversions at fixed intervals. if the trigger signal still is set when the conversion completes, a new conversion will not be started. if another positive edge occurs on the trigger signal during conversion, the edge will be ignored. note that an interrupt flag will be set even if the specific interrupt is disabled or the global interrupt enable bit in sreg is cleared. a conversion can thus be triggered without causing an interrupt. however, the interrupt flag must be cleared in order to trig- ger a new conversion at the next interrupt event. figure 83. adc auto trigger logic using the adc interrupt flag as a trigger source makes the adc start a new conversion as soon as the ongoing conversion has fini shed. the adc then operates in free run- ning mode, constantly sampling and updating the adc data register. the first conversion must be started by writing a logical one to the adsc bit in adcsra. in this mode the adc will perform successive conversions independently of whether the adc interrupt flag, adif is cleared or not. if auto triggering is enabled, single conversions can be started by writing adsc in adcsra to one. adsc can also be used to determine if a conversion is in progress. adsc adif source 1 source n adts[2:0] conversion logic prescaler start clk adc . . . . edge detector adate 195 atmega169v/l 2514j?avr?12/03 the adsc bit will be r ead as one during a conversion, independently of how the conver- sion was started. prescaling and conversion timing figure 84. adc prescaler by default, the successive approximation circuitry requires an input clock frequency between 50 khz and 200 khz to get maximum resolution. if a lower resolution than 10 bits is needed, the input clock frequency to the adc can be higher than 200 khz to get a higher sample rate. the adc module contains a prescaler, which generates an acceptable adc clock fre- quency from any cpu frequency above 100 khz. the prescaling is set by the adps bits in adcsra. the prescaler starts counting from the moment the adc is switched on by setting the aden bit in adcsra. the prescaler keeps running for as long as the aden bit is set, and is continuously reset when aden is low. when initiating a single ended conversion by setting the adsc bit in adcsra, the con- version starts at the following rising edge of the adc clock cycle. a normal conversion takes 13 adc clock cycles. the first conversion after the adc is switched on (aden in adcsra is set) takes 25 adc clock cycles in order to initialize the analog circuitry. the actual sample-and-hold takes place 1.5 adc clock cycles after the start of a normal conversion and 13.5 adc clock cycles after the start of an first conversion. when a con- version is complete, the result is written to the adc data registers, and adif is set. in single conversion mode, adsc is cleared simultaneously. the software may then set adsc again, and a new conversion will be initiated on the first rising adc clock edge. when auto triggering is used, the prescaler is reset when the trigger event occurs. this assures a fixed delay from the trigger event to the start of conversion. in this mode, the sample-and-hold takes place two adc clock cycles after the rising edge on the trigger source signal. three additional cpu clock cycles are used for synchronization logic. when using differential mode, along with auto triggering from a source other than the adc conversion complete, each conversion will require 25 adc clocks. this is because the adc must be disabled and re-enabled after every conversion. in free running mode, a new conversion will be started immediately after the conver- sion completes, while adsc remains high. for a summary of conversion times, see table 87. 7-bit adc prescaler adc clock source ck adps0 adps1 adps2 ck/128 ck/2 ck/4 ck/8 ck/16 ck/32 ck/64 reset aden start 196 atmega169v/l 2514j?avr?12/03 figure 85. adc timing diagram, first conversion (single conversion mode) figure 86. adc timing diagram, single conversion figure 87. adc timing diagram, auto triggered conversion sign and msb of result lsb of result adc clock adsc sample & hold adif adch adcl cycle number aden 1 212 13 14 15 16 17 18 19 20 21 22 23 24 25 1 2 first conversion next conversion 3 mux and refs update mux and refs update conversion complete 1 2 3 4 5 6 7 8 9 10 11 12 13 sign and msb of result lsb of result adc clock adsc adif adch adcl cycle number 12 one conversion next conversion 3 sample & hold mux and refs update conversion complete mux and refs update 1 2 3 4 5 6 7 8 9 10 11 12 13 sign and msb of result lsb of result adc clock trigger source adif adch adcl cycle number 12 one conversion next conversion conversion complete prescaler reset adate prescaler reset sample & hold mux and refs update 197 atmega169v/l 2514j?avr?12/03 figure 88. adc timing diagram, free running conversion table 87. adc conversion time condition sample & hold (cycles from start of conversion) conversion time (cycles) first conversion 14.5 25 normal conversions, single ended 1.5 13 auto triggered conversions 2 13.5 11 12 13 sign and msb of result lsb of result adc clock adsc adif adch adcl cycle number 12 one conversion next conversion 34 conversion complete sample & hold mux and refs update 198 atmega169v/l 2514j?avr?12/03 changing channel or reference selection the muxn and refs1:0 bits in the admux register are single buffered through a tem- porary register to which the cpu has random access. this ensures that the channels and reference selection only takes place at a safe point during the conversion. the channel and reference selection is continuously updated until a conversion is started. once the conversion starts, the channel and reference selection is locked to ensure a sufficient sampling time for the adc. continuous updating resumes in the last adc clock cycle before the conversion completes (adif in adcsra is set). note that the conversion starts on the following rising adc clock edge after adsc is written. the user is thus advised not to write new channel or reference selection values to admux until one adc clock cycle after adsc is written. if auto triggering is used, the exact time of the triggering event can be indeterministic. special care must be taken when updating the admux register, in order to control which conversion will be affected by the new settings. if both adate and aden is written to one, an interrupt event can occur at any time. if the admux register is changed in this period, the user cannot tell if the next conversion is based on the old or the new settings. admux can be safely updated in the following ways: 1. when adate or aden is cleared. 2. during conversion, minimum one adc clock cycle after the trigger event. 3. after a conversion, before the interrupt flag used as trigger source is cleared. when updating admux in one of these conditions, the new settings will affect the next adc conversion. adc input channels when changing channel selections, the user should observe the following guidelines to ensure that the correct channel is selected: in single conversion mode, always select the channel before starting the conversion. the channel selection may be changed one adc clock cycle after writing one to adsc. however, the simplest method is to wait for the conversion to complete before changing the channel selection. in free running mode, always select the channel before starting the first conversion. the channel selection may be changed one adc clock cycle after writing one to adsc. however, the simplest method is to wait for the first conversion to complete, and then change the channel selection. since the next conversion has already started automati- cally, the next result will reflect the previous channel selection. subsequent conversions will reflect the new channel selection. adc voltage reference the reference voltage for the adc (v ref ) indicates the conversion range for the adc. single ended channels that exceed v ref will result in codes close to 0x3ff. v ref can be selected as either avcc, internal 1.1v reference, or external aref pin. avcc is connected to the adc through a passive switch. the internal 1.1v reference is generated from the internal bandgap reference (v bg ) through an internal amplifier. in either case, the external aref pin is directly connected to the adc, and the reference voltage can be made more immune to noise by connecting a capacitor between the aref pin and ground. v ref can also be measured at the aref pin with a high impedant voltmeter. note that v ref is a high impedant source, and only a capacitive load should be connected in a system. if the user has a fixed voltage source connected to the aref pin, the user may not use the other reference voltage options in the application, as they will be shorted to the 199 atmega169v/l 2514j?avr?12/03 external voltage. if no external voltage is applied to the aref pin, the user may switch between avcc and 1.1v as reference selection. the first adc conversion result after switching reference voltage source may be inaccurate, and the user is advised to dis- card this result. adc noise canceler the adc features a noise canceler that enables conversion during sleep mode to reduce noise induced from the cpu core and other i/o peripherals. the noise canceler can be used with adc noise reduction and idle mode. to make use of this feature, the following procedure should be used: 1. make sure that the adc is enabled and is not busy converting. single con- version mode must be selected and the adc conversion complete interrupt must be enabled. 2. enter adc noise reduction mode (or idle mode). the adc will start a con- version once the cpu has been halted. 3. if no other interrupts occur before the adc conversion completes, the adc interrupt will wake up the cpu and execute the adc conversion complete interrupt routine. if another interrupt wakes up the cpu before the adc con- version is complete, that interrupt will be executed, and an adc conversion complete interrupt request will be generated when the adc conversion completes. the cpu will remain in active mode until a new sleep command is executed. note that the adc will not be automatically turned off when entering other sleep modes than idle mode and adc noise reduction mode. the user is advised to write zero to aden before entering such sleep modes to avoid excessive power consumption. 200 atmega169v/l 2514j?avr?12/03 analog input circuitry the analog input circuitry for single ended channels is illustrated in figure 89. an analog source applied to adcn is subjected to the pin capacitance and input leakage of that pin, regardless of whether that channel is selected as input for the adc. when the chan- nel is selected, the source must drive the s/h capacitor through the series resistance (combined resistance in the input path). the adc is optimized for analog signals with an output impedance of approximately 10 k ? or less. if such a source is used, the sampling time will be negligible. if a source with higher impedance is used, the sampling time will depend on how long time the source needs to charge the s/h capacitor, with can vary widely. the user is recom- mended to only use low impedant sources with slowly varying signals, since this minimizes the required charge transfer to the s/h capacitor. signal components higher than the nyquist frequency (f adc /2) should not be present for either kind of channels, to avoid distortion from unpredictable signal convolution. the user is advised to remove high frequency components with a low-pass filter before applying the signals as inputs to the adc. figure 89. analog input circuitry adcn i ih 1..100 k ? c s/h = 14 pf v cc /2 i il 201 atmega169v/l 2514j?avr?12/03 analog noise canceling techniques digital circuitry inside and outside the device generates emi which might affect the accuracy of analog measurements. if conversion accuracy is critical, the noise level can be reduced by applying the following techniques: 1. keep analog signal paths as short as possible. make sure analog tracks run over the analog ground plane, and keep them well away from high-speed switching digital tracks. 2. the avcc pin on the device should be connected to the digital v cc supply voltage via an lc network as shown in figure 90. 3. use the adc noise canceler function to reduce induced noise from the cpu. 4. if any adc port pins are used as digital outputs, it is essential that these do not switch while a conversion is in progress. figure 90. adc power connections vcc gnd 100nf analog ground plane (adc0) pf0 (adc7) pf7 (adc1) pf1 (adc2) pf2 (adc3) pf3 (adc4) pf4 (adc5) pf5 (adc6) pf6 aref gnd avcc 52 53 54 55 56 57 58 59 60 61 61 62 62 63 63 64 64 1 51 lcdcap pa0 10 ? 202 atmega169v/l 2514j?avr?12/03 adc accuracy definitions an n-bit single-ended adc converts a voltage linearly between gnd and v ref in 2 n steps (lsbs). the lowest code is read as 0, and the highest code is read as 2 n -1. several parameters describe the deviation from the ideal behavior: offset: the deviation of the first transition (0x000 to 0x001) compared to the ideal transition (at 0.5 lsb). ideal value: 0 lsb. figure 91. offset error gain error: after adjusting for offset, the gain error is found as the deviation of the last transition (0x3fe to 0x3ff) compared to the ideal transition (at 1.5 lsb below maximum). ideal value: 0 lsb figure 92. gain error integral non-linearity (inl): after adjusting for offset and gain error, the inl is the maximum deviation of an actual transition compared to an ideal transition for any code. ideal value: 0 lsb. output code v ref input voltage ideal adc actual adc offset error output code v ref input voltage ideal adc actual adc gain error 203 atmega169v/l 2514j?avr?12/03 figure 93. integral non-linearity (inl) differential non-linearity (dnl): the maximum deviation of the actual code width (the interval between two adjacent transitions) from the ideal code width (1 lsb). ideal value: 0 lsb. figure 94. differential non-linearity (dnl) quantization error: due to the quantization of the input voltage into a finite number of codes, a range of input voltages (1 lsb wide) will code to the same value. always 0.5 lsb. absolute accuracy: the maximum deviation of an actual (unadjusted) transition compared to an ideal transition for any code. this is the compound effect of offset, gain error, differential error, non-linearity, and quantization error. ideal value: 0.5 lsb. output code v ref input voltage ideal adc actual adc inl output code 0x3ff 0x000 0 v ref input voltage dnl 1 lsb 204 atmega169v/l 2514j?avr?12/03 adc conversion result after the conversion is complete (adif is high), the conversion result can be found in the adc result registers (adcl, adch). for single ended conversion, the result is where v in is the voltage on the selected input pin and v ref the selected voltage refer- ence (see table 89 on page 205 and table 90 on page 206). 0x000 represents analog ground, and 0x3ff represents the selected reference voltage minus one lsb. figure 95. differential measurement range adc v in 1024 ? v ref -------------------------- = adc v pos v neg ? () 512 ? v ref ---------------------------------------------------- - = 0 output code 0x1ff 0x000 v ref differential input voltage (volts) 0x3ff 0x200 - v ref 205 atmega169v/l 2514j?avr?12/03 admux = 0xfb (adc3 - adc2, 1.1v reference, left adjusted result) voltage on adc3 is 300 mv, voltage on adc2 is 500 mv. adcr = 512 * (300 - 500) / 1100 = -93 = 0x3a3 . adcl will thus read 0xc0, and adch will read 0xd8. writing zero to adlar right adjusts the result: adcl = 0xa3, adch = 0x03. adc multiplexer selection register ? admux bit 7:6 ? refs1:0: reference selection bits these bits select the voltage reference for the adc, as shown in table 89. if these bits are changed during a conversion, the change will not go in effect until this conversion is complete (adif in adcsra is set). the internal voltage reference options may not be used if an external reference voltage is being applied to the aref pin. bit 5 ? adlar: adc left adjust result the adlar bit affects the presentation of the adc conversion result in the adc data register. write one to adlar to left adjust the result. otherwise, the result is right adjusted. changing the adlar bit will affect the adc data register immediately, regardless of any ongoing conversions. for a complete description of this bit, see ?the adc data register ? adcl and adch? on page 208. table 88. correlation between input voltage and output codes v adcn read code corresponding decimal value v adcm + v ref 0x1ff 511 v adcm + 511 / 512 v ref 0x1ff 511 v adcm + 510 / 512 v ref 0x1fe 510 ... ... ... v adcm + 1 / 512 v ref 0x001 1 v adcm 0x000 0 v adcm - 1 / 512 v ref 0x3ff -1 ... ... ... v adcm - 511 / 512 v ref 0x201 -511 v adcm - v ref 0x200 -512 bit 76543210 refs1 refs0 adlar mux4 mux3 mux2 mux1 mux0 admux read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 table 89. voltage reference selections for adc refs1 refs0 voltage reference selection 0 0 aref, internal vref turned off 0 1 avcc with external capacitor at aref pin 10reserved 1 1 internal 1.1v voltage reference with external capacitor at aref pin 206 atmega169v/l 2514j?avr?12/03 bits 4:0 ? mux4:0: analog channel selection bits the value of these bits selects which combination of analog inputs are connected to the adc. see table 90 for details. if these bits are changed during a conversion, the change will not go in effect until this conversion is complete (adif in adcsra is set). table 90. input channel selections mux4..0 single ended input positive differential input negative differential input 00000 adc0 n/a 00001 adc1 00010 adc2 00011 adc3 00100 adc4 00101 adc5 00110 adc6 00111 adc7 01000 01001 01010 01011 01100 01101 01110 01111 10000 adc0 adc1 10001 adc1 adc1 10010 n/a adc2 adc1 10011 adc3 adc1 10100 adc4 adc1 10101 adc5 adc1 10110 adc6 adc1 10111 adc7 adc1 11000 adc0 adc2 11001 adc1 adc2 11010 adc2 adc2 11011 adc3 adc2 11100 adc4 adc2 11101 adc5 adc2 11110 1.1v (v bg ) n/a 11111 0v (gnd) 207 atmega169v/l 2514j?avr?12/03 adc control and status register a ? adcsra bit 7 ? aden: adc enable writing this bit to one enables the adc. by writing it to zero, the adc is turned off. turn- ing the adc off while a conversion is in progress, will terminate this conversion. bit 6 ? adsc: adc start conversion in single conversion mode, write this bit to one to start each conversion. in free run- ning mode, write this bit to one to start the first conversion. the first conversion after adsc has been written after the adc has been enabled, or if adsc is written at the same time as the adc is enabled, will ta ke 25 adc clock cycles instead of the normal 13. this first conversion performs initialization of the adc. adsc will read as one as long as a conversi on is in progress. when the conversion is complete, it returns to zero. writing zero to this bit has no effect. bit 5 ? adate: adc auto trigger enable when this bit is written to one, auto triggering of the adc is enabled. the adc will start a conversion on a positive edge of the selected trigger signal. the trigger source is selected by setting the adc trigger select bits, adts in adcsrb. bit 4 ? adif: adc interrupt flag this bit is set when an adc conversion completes and the data registers are updated. the adc conversion complete interrupt is executed if the adie bit and the i-bit in sreg are set. adif is cleared by hardware when executing the corresponding interrupt handling vector. alternatively, adif is cleared by writing a logical one to the flag. beware that if doing a read-modify-write on adcsra, a pending interrupt can be dis- abled. this also applies if the sbi and cbi instructions are used. bit 3 ? adie: adc interrupt enable when this bit is written to one and the i-bit in sreg is set, the adc conversion com- plete interrupt is activated. bit 76543210 aden adsc adate adif adie adps2 adps1 adps0 adcsra read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 208 atmega169v/l 2514j?avr?12/03 bits 2:0 ? adps2:0: adc prescaler select bits these bits determine the division factor between the xtal frequency and the input clock to the adc. the adc data register ? adcl and adch adlar = 0 adlar = 1 when an adc conversion is complete, the result is found in these two registers. when adcl is read, the adc data register is not updated until adch is read. consequently, if the result is left adjusted and no more than 8-bit precision is required, it is sufficient to read adch. otherwise, adcl must be read first, then adch. the adlar bit in admux, and the muxn bits in admux affect the way the result is read from the registers. if adlar is set, the result is left adjusted. if adlar is cleared (default), the result is right adjusted. adc9:0: adc conversion result these bits represent the result from the conversion, as detailed in ?adc conversion result? on page 204. table 91. adc prescaler selections adps2 adps1 adps0 division factor 000 2 001 2 010 4 011 8 100 16 101 32 110 64 1 1 1 128 bit 151413121110 9 8 ?????? adc9 adc8 adch adc7 adc6 adc5 adc4 adc3 adc2 adc1 adc0 adcl 76543210 read/writerrrrrrrr rrrrrrrr initial value00000000 00000000 bit 151413121110 9 8 adc9 adc8 adc7 adc6 adc5 adc4 adc3 adc2 adch adc1 adc0 ?????? adcl 76543210 read/writerrrrrrrr rrrrrrrr initial value00000000 00000000 209 atmega169v/l 2514j?avr?12/03 adc control and status register b ? adcsrb bit 7 ? res: reserved bit this bit is reserved for future use. to ensure compatibility with future devices, this bit must be written to zero when adcsrb is written. bit 2:0 ? adts2:0: adc auto trigger source if adate in adcsra is written to one, the value of these bits selects which source will trigger an adc conversion. if adate is cleared, the adts2:0 settings will have no effect. a conversion will be triggered by the rising edge of the selected interrupt flag. note that switching from a trigger source that is cleared to a trigger source that is set, will generate a positive edge on the trigger signal. if aden in adcsra is set, this will start a conversion. switching to free running mode (adts[2:0]=0) will not cause a trig- ger event, even if the adc interrupt flag is set . digital input disable register 0 ? didr0 bit 7..0 ? adc7d..adc0d: adc7..0 digital input disable when this bit is written logic one, the digital input buffer on the corresponding adc pin is disabled. the corresponding pin register bit will always read as zero when this bit is set. when an analog signal is applied to the adc7..0 pin and the digital input from this pin is not needed, this bit should be written logic one to reduce power consumption in the digital input buffer. bit 76543210 ? acme ? ? ? adts2 adts1 adts0 adcsrb read/write r r/w r r r r/w r/w r/w initial value 0 0 0 0 0 0 0 0 table 92. adc auto trigger source selections adts2 adts1 adts0 trigger source 0 0 0 free running mode 0 0 1 analog comparator 0 1 0 external interrupt request 0 0 1 1 timer/counter0 compare match 1 0 0 timer/counter0 overflow 1 0 1 timer/counter compare match b 1 1 0 timer/counter1 overflow 1 1 1 timer/counter1 capture event bit 76543210 adc7d adc6d adc5d adc4d adc3d adc2d adc1d adc0d didr0 read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 210 atmega169v/l 2514j?avr?12/03 lcd controller the lcd controller/driver is intended for monochrome passive liquid crystal display (lcd) with up to four common terminals and up to 25 segment terminals. features display capacity of 25 segment and four common terminals latching of display data gives full freedom in register update support static, 1/2, 1/3 and 1/4 duty support static, 1/2, 1/3 bias display possible in power-save mode for low power consumption low power waveform software selectable flexible selection of frame frequency software selection between system clock or an external asynchronous clock source on-chip lcd power supply, only one external capacitor needed lcd output voltage (contrast) software selectable from 2.6 to 3.35v for v cc in the entire operating range equal source and sink capability to increase lcd life time lcd interrupt can be used for display data update or wake-up from sleep mode segment and common pins not needed for driving the display can be used as ordinary i/o pins overview a simplified block diagram of the lcd controller/driver is shown in figure 96. for the actual placement of i/o pins, refer to ?pinout atmega169? on page 2. an lcd consists of several segments (pixels or complete symbols) which can be visible or non visible. a segment has two electrodes with liquid crystal between them. when a voltage above a threshold voltage is applied across the liquid crystal, the segment becomes visible. the voltage must alternate to avoid an electrophoresis effect in the liquid crystal, which degrades the display. hence the waveform across a segment must not have a dc- component. definitions several terms are used when describing lcd. the definitions in table 1 are used throughout this document. table 93. definitions lcd a passive display panel with terminals leading directly to a segment segment the least viewing element (pixel) which can be on or off common denotes how many segments are connected to a segment terminal duty 1/(number of common terminals on a actual lcd display) bias 1/(number of voltage levels used driving a lcd display -1) frame rate number of times the lcd segments is energized per second. 211 atmega169v/l 2514j?avr?12/03 figure 96. block diagram lcd module lcd clock sources the lcd controller can be clocked by an internal synchronous or an external asynchro- nous clock source. the clock source clk lcd is by default equal to the system clock, clk i/o . when the lcdcs bit in the lcdcrb register is written to logic one, the clock source is taken from the tosc1 pin. the clock source must be stable to obtain accurate lcd timing and hence minimize dc voltage offset across lcd segments. lcd prescaler the prescaler consist of a 12-bit ripple counter and a 1- to 8-clock divider. the lcdps2:0 bits selects clk lcd divided by 16, 64, 128, 256, 512, 1024, 2048, or 4096. if a finer resolution rate is required, the lcdcd2:0 bits can be used to divide the clock further by 1 to 8. output from the clock divider clk lcd_ps is used as clock source for the lcd timing. lcd memory the display memory is available through i/o registers grouped for each common termi- nal. when a bit in the display memory is written to one, the corresponding segment is energized (on), and non-energized when a bit in the display memory is written to zero. to energize a segment, an absolute voltage above a certain threshold must be applied. this is done by letting the output voltage on corresponding com pin and seg pin have opposite phase. for display with more than one common, one (1/2 bias) or two (1/3 bias) additional voltage levels must be applied. otherwise, non-energized segments on com0 would be energized for all non-selected common. clock multiplexer 12-bit prescaler 0 1 divide by 1 to 8 lcd timing lcdcrb lcdfrr clk i/o tosc lcdcra d a t a b u s clk lcd /4096 clk lcd /2048 clk lcd /128 clk lcd /1024 clk lcd /512 clk lcd /256 clk lcd /64 clk lcd /16 analog switch array lcdcs lcdcd2:0 lcdps2:0 clk lcd seg0 seg1 seg2 seg3 seg4 seg5 seg6 seg7 seg8 seg9 seg10 seg11 seg12 seg13 seg14 seg15 seg16 seg17 seg18 seg19 seg20 seg21 seg22 seg23 seg24 com0 com1 com2 com3 lcd buffer/ driver v lcd lcddr 18 -15 lcddr 13 -10 lcddr 8 - 5 lcddr 3 - 0 latch array lcd ouput decoder lcdccr lcdcc3:0 contrast controller/ power supply clk lcd_ps lcd cap 25 x 4:1 mux lcd_voltage_ok 2/3 v lcd 1/2 v lcd 1/3 v lcd 212 atmega169v/l 2514j?avr?12/03 addressing com0 starts a frame by driving opposite phase with large amplitude out on com0 compared to none addressed com lines. non-energized segments are in phase with the addressed com0, and energized segments have opposite phase and large amplitude. for waveform figures refer to ?mode of operation? on page 212. latched data from lcddr3 - lcddr0 is multiplexed into the decoder. the decoder is controlled from the lcd timing and sets up signals controlling the analog switches to produce an output waveform. next, com1 is addressed, and latched data from lcddr8 - lcddr5 is input to decoder. addressing continuous until all com lines are addressed according to number of common (duty). the display data are latched before a new frame start. lcd contrast controller/power supply the peak value (v lcd ) on the output waveform determines the lcd contrast. v lcd is controlled by software from 2.6v to 3.35v independent of v cc . an internal signal inhibits output to the lcd until v lcd has reached its target value. lcdcap an external capacitor (typical > 470 nf) must be connected to the lcdcap pin as shown in figure 97. this capacitor acts as a reservoir for lcd power (v lcd ). a large capacitance reduces ripple on v lcd but increases the time until vlcd reaches its target value. figure 97. lcdcap connection lcd buffer driver intermediate voltage levels are generated from buffers/drivers. to reduce power con- sumption, buffers are active until output voltage levels are within 10 mv. then lcd output pins are tri-stated and buffers are switched off. mode of operation static duty and bias if all segments on a lcd have one electrode common, then each segment must have a unique terminal. this kind of display is driven with the waveform shown in figure 98. seg0 - com0 is the voltage across a segment that is on, and seg1 - com0 is the voltage across a seg- ment that is off. 3 2 1 64 63 62 lcdcap 213 atmega169v/l 2514j?avr?12/03 figure 98. driving a lcd with one common terminal 1/2 duty and 1/2 bias for lcd with two common terminals (1/2 duty) a more complex waveform must be used to individually control segments. although 1/3 bias can be selected 1/2 bias is most common for these displays. waveform is shown in figure 99. seg0 - com0 is the volt- age across a segment that is on, and seg0 - com1 is the voltage across a segment that is off. figure 99. driving a lcd with two common terminals v lcd gnd v lcd gnd v lcd gnd -v lcd seg0 com0 seg0 - com0 frame frame v lcd gnd v lcd gnd gnd seg1 com0 seg1 - com0 frame frame v lcd gnd v lcd 1 / 2 v lcd gnd v lcd 1 / 2 v lcd gnd -1 / 2 v lcd -v lcd seg0 com0 seg0 - com0 frame frame v lcd gnd v lcd 1 / 2 v lcd gnd v lcd 1 / 2 v lcd gnd -1 / 2 v lcd -v lcd seg0 com1 seg0 - com1 frame frame 214 atmega169v/l 2514j?avr?12/03 1/3 duty and 1/3 bias 1/3 bias is usually recommended for lcd with three common terminals (1/3 duty). waveform is shown in figure 100. seg0 - com0 is the voltage across a segment that is on and seg0-com1 is the voltage across a segment that is off. figure 100. driving a lcd with three common terminals 1/4 duty and 1/3 bias 1/3 bias is optimal for lcd displays with four common terminals (1/4 duty). waveform is shown in figure 101. seg0 - com0 is the voltage across a segment that is on and seg0 - com1 is the voltage across a segment that is off. figure 101. driving a lcd with four common terminals v lcd 2 / 3 v lcd 1 / 3 v lcd gnd v lcd 2 / 3 v lcd 1 / 3 v lcd gnd v lcd 2 / 3 v lcd 1 / 3 v lcd gnd - 1 / 3 v lcd - 2 / 3 v lcd -v lcd seg0 com0 seg0 - com0 frame frame v lcd 2 / 3 v lcd 1 / 3 v lcd gnd v lcd 2 / 3 v lcd 1 / 3 v lcd gnd v lcd 2 / 3 v lcd 1 / 3 v lcd gnd - 1 / 3 v lcd - 2 / 3 v lcd -v lcd seg0 com1 seg0 - com1 frame frame v lcd 2 / 3 v lcd 1 / 3 v lcd gnd v lcd 2 / 3 v lcd 1 / 3 v lcd gnd v lcd 2 / 3 v lcd 1 / 3 v lcd gnd - 1 / 3 v lcd - 2 / 3 v lcd -v lcd seg0 com0 seg0 - com0 frame frame v lcd 2 / 3 v lcd 1 / 3 v lcd gnd v lcd 2 / 3 v lcd 1 / 3 v lcd gnd v lcd 2 / 3 v lcd 1 / 3 v lcd gnd - 1 / 3 v lcd - 2 / 3 v lcd -v lcd seg0 com1 seg0 - com1 frame frame 215 atmega169v/l 2514j?avr?12/03 low power waveform to reduce toggle activity and hence power consumption a low power waveform can be selected by writing lcdab to one. low power waveform requires two subsequent frames with the same display data to obtain zero dc voltage. consequently data latch- ing and interrupt flag is only set every second frame. default and low power waveform is shown in figure 102 for 1/3 duty and 1/3 bias. for other selections of duty and bias, the effect is similar. figure 102. default and low power waveform operation in sleep mode when synchronous lcd clock is selected (lcdcs = 0) the lcd display will operate in idle mode and power-save mode with any clock source. an asynchronous clock from tosc1 can be selected as lcd clock by writing the lcdcs bit to one when calibrated internal rc oscillator is selected as system clock source. the lcd will then operate in idle mode, adc noise reduction mode and power-save mode. when exclk in assr register is written to one, and asynchronous clock is selected, the external clock input buffer is enabled and an external clock can be input on timer oscillator 1 (tosc1) pin instead of a 32 khz crystal. see ?asynchronous operation of the timer/counter? on page 138 for further details. before entering power-down mode, standby mode or adc noise reduction mode with synchronous lcd clock selected, the user have to disable the lcd. refer to ?disabling the lcd? on page 218. display blanking when lcdbl is written to one, the lcd is blanked after completing the current frame. all segments and common pins are connected to gnd, discharging the lcd. display memory is preserved. display blanking should be used before disabling the lcd to avoid dc voltage across segments, and a slowly fading image. port mask for lcd with less than 25 segment terminals, it is possible to mask some of the unused pins and use them as ordinary port pins instead. refer to table 95 for details. unused common pins are automatically configured as port pins. v lcd 2 / 3 v lcd 1 / 3 v lcd gnd v lcd 2 / 3 v lcd 1 / 3 v lcd gnd v lcd 2 / 3 v lcd 1 / 3 v lcd gnd - 1 / 3 v lcd - 2 / 3 v lcd -v lcd seg0 com0 seg0 - com0 frame frame v lcd 2 / 3 v lcd 1 / 3 v lcd gnd v lcd 2 / 3 v lcd 1 / 3 v lcd gnd v lcd 2 / 3 v lcd 1 / 3 v lcd gnd - 1 / 3 v lcd - 2 / 3 v lcd -v lcd seg0 com0 seg0 - com 0 frame frame 216 atmega169v/l 2514j?avr?12/03 lcd usage lcd initialization prior to enabling the lcd some initialization must be preformed. the initialization pro- cess normally consists of setting the frame rate, duty, bias and port mask. lcd contrast is set initially, but can also be adjusted during operation. consider the following lcd as an example: figure 103. display: tn positive, reflective number of common terminals: 3 number of segment terminals: 21 bias system: 1/3 bias drive system: 1/3 duty operating voltage: 3.3 0.9 v 1b 1c 2a 2b 2c 2e 2f 2d 2g com3 com0 com1 com2 seg0 seg1 seg2 1b,1c 2c 2f 2a 2d 2g 2b 2e .. com2 seg0 seg1 seg2 atmega169 com1 com0 connection table lcd 51 50 49 48 47 46 45 217 atmega169v/l 2514j?avr?12/03 note: 1. the example code assumes that the part specific header file is included. assembly code example (1) lcd_init: ; use 32 khz crystal oscillator ; 1/3 bias and 1/3 duty, seg21:seg24 is used as port pins ldi r16, (1< 219 atmega169v/l 2514j?avr?12/03 note: 1. the example code assumes that the part specific header file is included. assembly code example (1) lcd_disable: ; wait until a new frame is started. wait_1: lds r16, lcdcra sbrs r16, lcdif rjmp wait_1 ; set lcd blanking and clear interrupt flag ; by writing a logical one to the flag. ldi r16, (1< 221 atmega169v/l 2514j?avr?12/03 lcd control and status register b ? lcdcrb bit 7 ? lcdcs: lcd clock select when this bit is written to zero, the system clock is used. when this bit is written to one, the external asynchronous clock source is used. the asynchronous clock source is either timer/counter oscillator or external clock, depending on exclk in assr. see ?asynchronous operation of the timer/counter? on page 138 for further details. bit 6 ? lcd2b: lcd 1/2 bias select when this bit is written to zero, 1/3 bias is used. when this bit is written to one, ? bias is used. refer to the lcd manufacture for recommended bias selection. bit 5:4 ? lcdmux1:0: lcd mux select the lcdmux1:0 bits determine the duty cycle. common pins that are not used are ordi- nary port pins. the different duty selections are shown in table 94. note: 1. 1/2 bias when lcd2b is written to one and 1/3 otherwise. bit 3 ? res: reserved bit this bit is reserved bit in the atmega169 and will always read as zero. bit 765 43210 lcdcs lcd2b lcdmux1 lcdmux0 ? lcdpm2 lcdpm1 lcdpm0 lcdcrb read/write r/w r/w r/w r/w r r/w r/w r/w initial value 0 0 0 0 0 0 0 0 table 94. lcd duty select lcdmux1 lcdmux0 duty bias com pin i/o port pin 0 0 static static com0 com1:3 0 1 1/2 1/2 or 1/3 (1) com0:1 com2:3 101/31/2 or 1/3 (1) com0:2 com3 111/41/2 or 1/3 (1) com0:3 none 222 atmega169v/l 2514j?avr?12/03 bits 2:0 ? lcdpm2:0: lcd port mask the lcdpm2:0 bits determine the number of port pins to be used as segment drivers. the different selections are shown in table 95. unused pins can be used as ordinary port pins. lcd frame rate register ? lcdfrr bit 7 ? res: reserved bit this bit is reserved bit in the atmega169 and will always read as zero. bits 6:4 ? lcdps2:0: lcd prescaler select the lcdps2:0 bits selects tap point from a prescaler. the prescaled output can be fur- ther divided by setting the clock divide bits (lcdcd2:0). the different selections are shown in table 96. together they determine the prescaled lcd clock (clk lcd_ps ), which is clocking the lcd module. table 95. lcd port mask lcdpm2 lcdpm1 lcdpm0 i/o port in use as segment driver maximum number of segments 0 0 0 seg0:12 13 0 0 1 seg0:14 15 0 1 0 seg0:16 17 0 1 1 seg0:18 19 1 0 0 seg0:20 21 1 0 1 seg0:22 23 1 1 0 seg0:23 24 1 1 1 seg0:24 25 bit 76543210 ? lcdps2 lcdps1 lcdps0 ? lcdcd2 lcdcd1 lcdcd0 lcdfrr read/write r r/w r/w r/w r r/w r/w r/w initial value 0 0 0 0 0 0 0 0 table 96. lcd prescaler select lcdps2 lcdps1 lcdps0 output from prescaler clk lcd /n applied prescaled lcd clock frequency when lcdcd2:0 = 0, duty = 1/4, and frame rate = 64 hz 000clk lcd /16 8.1 khz 001clk lcd /64 33 khz 010clk lcd /128 66 khz 011clk lcd /256 130 khz 100clk lcd /512 260 khz 101clk lcd /1024 520 khz 110clk lcd /2048 1 mhz 111clk lcd /4096 2 mhz 223 atmega169v/l 2514j?avr?12/03 bit 3 ? res: reserved bit this bit is reserved bit in the atmega169 and will always read as zero. bits 2:0 ? lcdcd2:0: lcd clock divide 2, 1, and 0 the lcdcd2:0 bits determine division ratio in the clock divider. the various selections are shown in table 97. this clock divider gives extra flexibility in frame rate selection. the frame frequency can be calculated by the following equation: where: n = prescaler divider (16, 64, 128, 256, 512, 1024, 2048, or 4096). k = 8 for duty = 1/4, 1/2, and static. k = 6 for duty = 1/3. this is a very flexible scheme, and users are encouraged to calculate their own table to investigate the possible frame rates from the formula above. note when using 1/3 duty the frame rate is increased with 33% when frame rate register is constant. example of frame rate calculation is shown in table 98. table 97. lcd clock divide lcdcd2 lcdcd1 lcdcd0 output from prescaler divided by: clk lcd = 32.768 khz, n = 16, and duty = 1/4, gives a frame rate of: 0 0 0 1 256 hz 0 0 1 2 128 hz 0 1 0 3 85.3 hz 011 4 64 hz 1 0 0 5 51.2 hz 1 0 1 6 42.7 hz 1 1 0 7 36.6 hz 111 8 32 hz table 98. example of frame rate calculation ckl lcd duty k lcdps2:0 n lcdcs2:0 frame rate 4 mhz 1/4 8 6 2048 3 4000000/(8*2048*(1+3)) = 61 hz 4 mhz 1/3 6 6 2048 3 4000000/(6*2048*(1+3)) = 81 hz 32.768 khz static 8 0 16 0 32768/(8*16*(1+0)) = 256 hz 32.768 khz 1/2 8 0 16 4 32768/(8*16*(1+4)) = 51 hz f frame f clk lcd kn 1 lcdcd + () ?? () --------------------------------------------------------- = 224 atmega169v/l 2514j?avr?12/03 lcd contrast control register ? lcdccr bits 7:4 ? res: reserved bits these bits are reserved bits in the atmega169 and will always read as zero. bits 3:0 ? lcdcc3:0: lcd contrast control the lcdcc3:0 bits determine the maximum voltage vlcd on segment and common pins. the different selections are shown in table 99. new values take effect every beginning of a new frame. bit 76543210 ? ? ? ? lcdcc3 lcdcc2 lcdcc1 lcdcc0 lcdccr read/write r r r r r/w r/w r/w r/w initial value00000000 table 99. lcd contrast control lcdcc3 lcdcc2 lcdcc1 lcdcc0 maximum voltage v ldc 0000 2.60 0001 2.65 0010 2.70 0011 2.75 0100 2.80 0101 2.85 0110 2.90 0111 2.95 1000 3.00 1001 3.05 1010 3.10 1011 3.15 1100 3.20 1101 3.25 1110 3.30 1111 3.35 225 atmega169v/l 2514j?avr?12/03 lcd memory mapping write a lcd memory bit to one and the corresponding segment will be energized (visi- ble). unused lcd memory bits for the actual display can be used freely as storage. bit 76543210 ? ? ? ? ? ? ? ? lcddr19 com3 ? ? ? ? ? ? ? seg324 lcddr18 com3 seg323 seg322 seg321 seg320 seg319 seg318 seg317 seg316 lcddr17 com3 seg315 seg314 seg313 seg312 seg311 seg310 seg309 seg308 lcddr16 com3 seg307 seg306 seg305 seg304 seg303 seg302 seg301 seg300 lcddr15 ? ? ? ? ? ? ? ? lcddr14 com2 ? ? ? ? ? ? ? seg224 lcddr13 com2 seg223 seg222 seg221 seg220 seg219 seg218 seg217 seg216 lcddr12 com2 seg215 seg214 seg213 seg212 seg211 seg210 seg209 seg208 lcddr11 com2 seg207 seg206 seg205 seg204 seg203 seg202 seg201 seg200 lcddr10 ? ? ? ? ? ? ? ? lcddr9 com1 ? ? ? ? ? ? ? seg124 lcddr8 com1 seg123 seg122 seg121 seg120 seg119 seg118 seg117 seg116 lcddr7 com1 seg115 seg114 seg113 seg112 seg111 seg110 seg109 seg108 lcddr6 com1 seg107 seg106 seg105 seg104 seg103 seg102 seg101 seg100 lcddr5 ? ? ? ? ? ? ? ? lcddr4 com0 ? ? ? ? ? ? ? seg024 lcddr3 com0 seg023 seg022 seg021 seg020 seg019 seg018 seg017 seg016 lcddr2 com0 seg015 seg014 seg013 seg012 seg011 seg010 seg009 seg008 lcddr1 com0 seg007 seg006 seg005 seg004 seg003 seg002 seg001 seg000 lcddr0 read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 00000000 226 atmega169v/l 2514j?avr?12/03 jtag interface and on-chip debug system features jtag (ieee std. 1149.1 compliant) interface boundary-scan capabilities according to the ieee std. 1149.1 (jtag) standard debugger a ccess to: ? all internal peripheral units ? internal and external ram ? the internal register file ?program counter ? eeprom and flash memories extensive on-chip debug support for break conditions, including ? avr break instruction ? break on change of program memory flow ? single step break ? program memory break points on single address or address range ? data memory break points on single address or address range programming of flash, eeprom, fuses, and lock bits through the jtag interface on-chip debugging supported by avr studio ? overview the avr ieee std. 1149.1 compliant jtag interface can be used for testing pcbs by using the jtag boundary-scan capability programming the non-volatile memories, fuses and lock bits on-chip debugging a brief description is given in the following sections. detailed descriptions for program- ming via the jtag interface, and using the boundary-scan chain can be found in the sections ?programming via the jtag interface? on page 285 and ?ieee 1149.1 (jtag) boundary-scan? on page 232 , respectively. the on-chip debug support is considered being private jtag instructions, and distributed within atmel and to selected third party vendors only. figure 104 shows a block diagram of the jtag interface and the on-chip debug sys- tem. the tap controller is a state machine controlled by the tck and tms signals. the tap controller selects either the jtag instruction register or one of several data reg- isters as the scan chain (shift register) between the tdi ? input and tdo ? output. the instruction register holds jtag instructions controlling the behavior of a data register. the id-register, bypass register, and the boundary-scan chain are the data registers used for board-level testing. the jtag programming interface (actually consisting of several physical and virtual data registers) is used for serial programming via the jtag interface. the internal scan chain and break point scan chain are used for on-chip debugging only. test access port ? tap the jtag interface is accessed through four of the avr?s pins. in jtag terminology, these pins constitute the test access port ? tap. these pins are: tms: test mode select. this pin is used for navigating through the tap-controller state machine. tck: test clock. jtag operation is synchronous to tck. tdi: test data in. serial input data to be shifted in to the instruction register or data register (scan chains). tdo: test data out. serial output data from instruction register or data register. 227 atmega169v/l 2514j?avr?12/03 the ieee std. 1149.1 also specifies an optional tap signal; trst ? test reset ? which is not provided. when the jtagen fuse is unprogrammed, these four tap pins are normal port pins and the tap controller is in reset. when programmed and the jtd bit in mcucsr is cleared, the tap input signals are internally pulled high and the jtag is enabled for boundary-scan and programming. in this case, the tap output pin (tdo) is left floating in states where the jtag tap controller is not shifting data, and must therefore be con- nected to a pull-up resistor or other hardware having pull-ups (for instance the tdi-input of the next device in the scan chain). the device is shipped with this fuse programmed. for the on-chip debug system, in addition to the jtag interface pins, the reset pin is monitored by the debugger to be able to detect external reset sources. the debugger can also pull the reset pin low to reset the whole system, assuming only open collec- tors on the reset line are used in the application. figure 104. block diagram tap controller tdi tdo tck tms flash memory avr cpu digital peripheral units jtag / avr core communication interface breakpoint unit flow control unit ocd status and control internal scan chain m u x instruction register id register bypass register jtag programming interface pc instruction address data breakpoint scan chain address decoder analog peripherial units i/o port 0 i/o port n boundary scan chain analog inputs control & clock lines device boundary 228 atmega169v/l 2514j?avr?12/03 figure 105. tap controller state diagram tap controller the tap controller is a 16-state finite state machine that controls the operation of the boundary-scan circuitry, jtag programming circuitry, or on-chip debug system. the state transitions depicted in figure 105 depend on the signal present on tms (shown adjacent to each state transition) at the time of the rising edge at tck. the initial state after a power-on reset is test-logic-reset. as a definition in this document, the lsb is shifted in and out first for all shift registers. assuming run-test/idle is the present state, a typical scenario for using the jtag inter- face is: at the tms input, apply the sequence 1, 1, 0, 0 at the rising edges of tck to enter the shift instruction register ? shift-ir state. while in this state, shift the four bits of the jtag instructions into the jtag instruction register from the tdi input at the rising edge of tck. the tms input must be held low during input of the 3 lsbs in order to remain in the shift-ir state. the msb of the instruction is shifted in when this state is left by setting tms high. while the instruction is shifted in from the tdi pin, the captured ir-state 0x01 is shifted out on the tdo pin. the jtag instruction selects a particular data register as path between tdi and tdo and controls the circuitry surrounding the selected data register. apply the tms sequence 1, 1, 0 to re-enter the run-test/idle state. the instruction is latched onto the parallel output from the shift register path in the update-ir test-logic-reset run-test/idle shift-dr exit1-dr pause-dr exit2-dr update-dr select-ir scan capture-ir shift-ir exit1-ir pause-ir exit2-ir update-ir select-dr scan capture-dr 0 1 0 11 1 00 00 11 1 0 1 1 0 1 0 0 1 0 1 1 0 1 0 0 0 0 1 1 229 atmega169v/l 2514j?avr?12/03 state. the exit-ir, pause-ir, and exit2-ir states are only used for navigating the state machine. at the tms input, apply the sequence 1, 0, 0 at the rising edges of tck to enter the shift data register ? shift-dr state. while in this state, upload the selected data register (selected by the present jtag instruction in the jtag instruction register) from the tdi input at the rising edge of tck. in order to remain in the shift-dr state, the tms input must be held low during input of all bits except the msb. the msb of the data is shifted in when this state is left by setting tms high. while the data register is shifted in from the tdi pin, the parallel inputs to the data register captured in the capture-dr state is shifted out on the tdo pin. apply the tms sequence 1, 1, 0 to re-enter the run-test/idle state. if the selected data register has a latched parallel-output, the latching takes place in the update- dr state. the exit-dr, pause-dr, and exit2-dr states are only used for navigating the state machine. as shown in the state diagram, the run-test/idle state need not be entered between selecting jtag instruction and using data registers, and some jtag instructions may select certain functions to be performed in the run-test/idle, making it unsuitable as an idle state. note: independent of the initial state of the tap controller, the test-logic-reset state can always be entered by holding tms high for five tck clock periods. for detailed information on the jtag specification, refer to the literature listed in ?bibli- ography? on page 231. using the boundary- scan chain a complete description of the boundary-scan capabilities are given in the section ?ieee 1149.1 (jtag) boundary-scan? on page 232. using the on-chip debug system as shown in figure 104, the hardware support for on-chip debugging consists mainly of a scan chain on the interface between the internal avr cpu and the internal peripheral units. break point unit. communication interface between the cpu and jtag system. all read or modify/write operations needed for implementing the debugger are done by applying avr instructions via the internal avr cpu scan chain. the cpu sends the result to an i/o memory mapped location which is part of the communication interface between the cpu and the jtag system. the break point unit implements break on change of program flow, single step break, two program memory break points , and two combined break points. together, the four break points can be configured as either: 4 single program memory break points. 3 single program memory break point + 1 single data memory break point. 2 single program memory break points + 2 single data memory break points. 2 single program memory break points + 1 program memory break point with mask (?range break point?). 2 single program memory break points + 1 data memory break point with mask (?range break point?). a debugger, like the avr studio, may however use one or more of these resources for its internal purpose, leaving less flexibility to the end-user. 230 atmega169v/l 2514j?avr?12/03 a list of the on-chip debug specific jtag instructions is given in ?on-chip debug spe- cific jtag instructions? on page 230. the jtagen fuse must be programmed to enable the jtag test access port. in addi- tion, the ocden fuse must be programmed and no lock bits must be set for the on- chip debug system to work. as a security feature, the on-chip debug system is disabled when either of the lb1 or lb2 lock bits are set. otherwise, the on-chip debug system would have provided a back-door into a secured device. the avr studio enables the user to fully control execution of programs on an avr device with on-chip debug capability, avr in-circuit emulator, or the built-in avr instruction set simulator. avr studio ? supports source level execution of assembly programs assembled with atmel corporation?s avr assembler and c programs com- piled with third party vendors? compilers. avr studio runs under microsoft ? windows ? 95/98/2000, windows nt ? and windows xp ? . for a full description of the avr studio, please refer to the avr studio user guide. only highlights are presented in this document. all necessary execution commands are available in avr studio, both on source level and on disassembly level. the user can execute the program, single step through the code either by tracing into or stepping over functions, step out of functions, place the cursor on a statement and execute until the statement is reached, stop the execution, and reset the execution target. in addition, the user can have an unlimited number of code break points (using the break instruction) and up to two data memory break points, alternatively combined as a mask (range) break point. on-chip debug specific jtag instructions the on-chip debug support is considered being private jtag instructions, and distrib- uted within atmel and to selected third party vendors only. instruction opcodes are listed for reference. private0; 0x8 private jtag instruction for accessing on-chip debug system. private1; 0x9 private jtag instruction for accessing on-chip debug system. private2; 0xa private jtag instruction for accessing on-chip debug system. private3; 0xb private jtag instruction for accessing on-chip debug system. 231 atmega169v/l 2514j?avr?12/03 on-chip debug related register in i/o memory on-chip debug register ? ocdr the ocdr register provides a communication channel from the running program in the microcontroller to the debugger. the cpu can transfer a byte to the debugger by writing to this location. at the same time, an internal flag; i/o debug register dirty ? idrd ? is set to indicate to the debugger that the register has been written. when the cpu reads the ocdr register the 7 lsb will be from the ocdr register, while the msb is the idrd bit. the debugger clears the idrd bit when it has read the information. in some avr devices, this register is shared with a standard i/o location. in this case, the ocdr register can only be accessed if the ocden fuse is programmed, and the debugger enables access to the ocdr register. in all other cases, the standard i/o location is accessed. refer to the debugger documentation for further information on how to use this register. using the jtag programming capabilities programming of avr parts via jtag is performed via the 4-pin jtag port, tck, tms, tdi, and tdo. these are the only pins that need to be controlled/observed to perform jtag programming (in addition to power pins). it is not required to apply 12v externally. the jtagen fuse must be programmed and the jtd bit in the mcucr register must be cleared to enable the jtag test access port. the jtag programming capability supports: flash programming and verifying. eeprom programming and verifying. fuse programming and verifying. lock bit programming and verifying. the lock bit security is exactly as in parallel programming mode. if the lock bits lb1 or lb2 are programmed, the ocden fuse cannot be programmed unless first doing a chip erase. this is a security feature that ensures no back-door exists for reading out the content of a secured device. the details on programming through the jtag interface and programming specific jtag instructions are given in the section ?programming via the jtag interface? on page 285. bibliography for more information about general boundary-scan, the following literature can be consulted: ieee: ieee std. 1149.1-1990. ieee standard test access port and boundary-scan architecture, ieee, 1993. colin maunder: the board designers guide to testable logic circuits, addison- wesley, 1992. bit 7 6543210 msb/idrd lsb ocdr read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0000000 232 atmega169v/l 2514j?avr?12/03 ieee 1149.1 (jtag) boundary-scan features jtag (ieee std. 1149.1 compliant) interface boundary-scan capabilities according to the jtag standard full scan of all port functions as well as analog circuitry having off-chip connections supports the optional idcode instruction additional public avr_reset instruction to reset the avr system overview the boundary-scan chain has the capability of driving and observing the logic levels on the digital i/o pins, as well as the boundary between digital and analog logic for analog circuitry having off-chip connections. at system level, all ics having jtag capabilities are connected serially by the tdi/tdo signals to form a long shift register. an external controller sets up the devices to drive values at their output pins, and observe the input values received from other devices. the controller compares the received data with the expected result. in this way, boundary-scan provides a mechanism for testing intercon- nections and integrity of components on printed circuits boards by using the four tap signals only. the four ieee 1149.1 defined mandatory jtag instructions idcode, bypass, sam- ple/preload, and extest, as well as the avr specific public jtag instruction avr_reset can be used for testing the printed circuit board. initial scanning of the data register path will show the id-code of the device, since idcode is the default jtag instruction. it may be desirable to have the avr device in reset during test mode. if not reset, inputs to the device may be determined by the scan operations, and the internal software may be in an undetermined state when exiting the test mode. entering reset, the outputs of any port pin will instantly enter the high impedance state, making the highz instruction redundant. if needed, the bypass instruction can be issued to make the shortest possible scan chain through the device. the device can be set in the reset state either by pulling the external reset pin low, or issuing the avr_reset instruction with appropriate setting of the reset data register. the extest instruction is used for sampling external pins and loading output pins with data. the data from the output latch will be driven out on the pins as soon as the extest instruction is loaded into the jtag ir-register. therefore, the sample/pre- load should also be used for setting initial values to the scan ring, to avoid damaging the board when issuing the extest instruction for the first time. sample/preload can also be used for taking a snapshot of the external pins during normal operation of the part. the jtagen fuse must be programmed and the jtd bit in the i/o register mcucr must be cleared to enable the jtag test access port. when using the jtag interface for boundary-scan, using a jtag tck clock frequency higher than the internal chip frequency is possible. the chip clock is not required to run. data registers the data registers relevant for boundary-scan operations are: bypass register device identification register reset register boundary-scan chain 233 atmega169v/l 2514j?avr?12/03 bypass register the bypass register consists of a single shift register stage. when the bypass regis- ter is selected as path between tdi and tdo, the register is reset to 0 when leaving the capture-dr controller state. the bypass register can be used to shorten the scan chain on a system when the other devices are to be tested. device identification register figure 106 shows the structure of the device identification register. figure 106. the format of the device identification register version version is a 4-bit number identifying the revision of the component. the relevant version number is shown in table 100. part number the part number is a 16-bit code identifying the component. the jtag part number for atmega169 is listed in table 101. manufacturer id the manufacturer id is a 11-bit code identifying the manufacturer. the jtag manufac- turer id for atmel is listed in table 102. msb lsb bit 31 28 27 12 11 1 0 device id version part number manufacturer id 1 4 bits 16 bits 11 bits 1-bit table 100. jtag version numbers version jtag version number (hex) atmega169 revision a 0x0 atmega169 revision b 0x1 atmega169 revision c 0x2 atmega169 revision d 0x3 table 101. avr jtag part number part number jtag part number (hex) atmega169 0x9405 table 102. manufacturer id manufacturer jtag manufactor id (hex) atmel 0x01f 234 atmega169v/l 2514j?avr?12/03 reset register the reset register is a test data register used to reset the part. since the avr tri- states port pins when reset, the reset register can also replace the function of the unimplemented optional jtag instruction highz. a high value in the reset register corresponds to pulling the external reset low. the part is reset as long as there is a high value present in the reset register. depending on the fuse settings for the clock options, the part will remain reset for a reset time-out period (refer to ?clock sources? on page 24) after releasing the reset register. the out- put from this data register is not latched, so the reset will take place immediately, as shown in figure 107. figure 107. reset register boundary-scan chain the boundary-scan chain has the capability of driving and observing the logic levels on the digital i/o pins, as well as the boundary between digital and analog logic for analog circuitry having off-chip connections. see ?boundary-scan chain? on page 236 for a complete description. boundary-scan specific jtag instructions the instruction register is 4-bit wide, supporting up to 16 instructions. listed below are the jtag instructions useful for boundary-scan operation. note that the optional highz instruction is not implemented, but all outputs with tri-state capability can be set in high- impedant state by using the avr_reset instruction, since the initial state for all port pins is tri-state. as a definition in this datasheet, the lsb is shifted in and out first for all shift registers. the opcode for each instruction is shown behind the instruction name in hex format. the text describes which data register is selected as path between tdi and tdo for each instruction. dq from tdi clockdr avr_reset to tdo from other internal and external reset sources internal reset 235 atmega169v/l 2514j?avr?12/03 extest; 0x0 mandatory jtag instruction for selecting the boundary-scan chain as data register for testing circuitry external to the avr package. for port-pins, pull-up disable, output control, output data, and input data are all accessible in the scan chain. for analog cir- cuits having off-chip connections, the interface between the analog and the digital logic is in the scan chain. the contents of the latched outputs of the boundary-scan chain is driven out as soon as the jtag ir-register is loaded with the extest instruction. the active states are: capture-dr: data on the external pins are sampled into the boundary-scan chain. shift-dr: the internal scan chain is shifted by the tck input. update-dr: data from the scan chain is applied to output pins. idcode; 0x1 optional jtag instruction selecting the 32 bit id-register as data register. the id- register consists of a version number, a device number and the manufacturer code chosen by jedec. this is the default instruction after power-up. the active states are: capture-dr: data in the idcode register is sampled into the boundary-scan chain. shift-dr: the idcode scan chain is shifted by the tck input. sample_preload; 0x2 mandatory jtag instruction for pre-loading the output latches and taking a snap-shot of the input/output pins without affecting the system operation. however, the output latches are not connected to the pins. the boundary-scan chain is selected as data register. the active states are: capture-dr: data on the external pins are sampled into the boundary-scan chain. shift-dr: the boundary-scan chain is shifted by the tck input. update-dr: data from the boundary-scan chain is applied to the output latches. however, the output latches are not connected to the pins. avr_reset; 0xc the avr specific public jtag instruction for forcing the avr device into the reset mode or releasing the jtag reset source. the tap controller is not reset by this instruc- tion. the one bit reset register is selected as data register. note that the reset will be active as long as there is a logic ?one? in the reset chain. the output from this chain is not latched. the active states are: shift-dr: the reset register is shifted by the tck input. bypass; 0xf mandatory jtag instruction selecting the bypass register for data register. the active states are: capture-dr: loads a logic ?0? into the bypass register. shift-dr: the bypass register cell between tdi and tdo is shifted. 236 atmega169v/l 2514j?avr?12/03 boundary-scan related register in i/o memory mcu control register ? mcucr the mcu control register contains control bits for general mcu functions. bit 7 ? jtd: jtag interface disable when this bit is zero, the jtag interface is enabled if the jtagen fuse is programmed. if this bit is one, the jtag interface is disabled. in order to avoid unintentional disabling or enabling of the jtag interface, a timed sequence must be followed when changing this bit: the application software must write this bit to the desired value twice within four cycles to change its value. note that this bit must not be altered when using the on-chip debug system. if the jtag interface is left unconnected to other jtag circuitry, the jtd bit should be set to one. the reason for this is to avoid static current at the tdo pin in the jtag interface. mcu status register ? mcusr the mcu status register provides information on which reset source caused an mcu reset. bit 4 ? jtrf: jtag reset flag this bit is set if a reset is being caused by a logic one in the jtag reset register selected by the jtag instruction avr_reset. this bit is reset by a power-on reset, or by writing a logic zero to the flag. boundary-scan chain the boundary-scan chain has the capability of driving and observing the logic levels on the digital i/o pins, as well as the boundary between digital and analog logic for analog circuitry having off-chip connection. scanning the digital port pins figure 108 shows the boundary-scan cell for a bi-directional port pin with pull-up func- tion. the cell consists of a standard boundary-scan cell for the pull-up enable ? puexn ? function, and a bi-directional pin cell that combines the three signals output control ? ocxn, output data ? odxn, and input data ? idxn, into only a two-stage shift register. the port and pin indexes are not used in the following description the boundary-scan logic is not included in the figures in the datasheet. figure 109 shows a simple digital port pin as described in the section ?i/o-ports? on page 51. the boundary-scan details from figure 108 replaces the dashed box in figure 109. when no alternate port function is present, the input data ? id ? corresponds to the pinxn register value (but id has no synchronizer), output data corresponds to the port register, output control corresponds to the data direction ? dd register, and the pull-up enable ? puexn ? corresponds to logic expression pud ddxn portxn. bit 76543210 jtd ? ? pud ? ? ivsel ivce mcucr read/write r/w r r r/w r r r/w r/w initial value00000000 bit 76543210 ? ? ?jtrf wdrf borf extrf porf mcusr read/write r r r r/w r/w r/w r/w r/w initial value 0 0 0 see bit description 237 atmega169v/l 2514j?avr?12/03 digital alternate port functions are connected outside the dotted box in figure 109 to make the scan chain read the actual pin value. for analog function, there is a direct connection from the external pin to the analog circuit, and a scan chain is inserted on the interface between the digital logic and the analog circuitry. figure 108. boundary-scan cell for bi-directional port pin with pull-up function. dq dq g 0 1 0 1 dq dq g 0 1 0 1 0 1 0 1 dq dq g 0 1 port pin (pxn) vcc extest to next cell shiftdr output control (oc) pullup enable (pue) output data (od) input data (id) from last cell updatedr clockdr ff2 ld2 ff1 ld1 ld0 ff0 238 atmega169v/l 2514j?avr?12/03 figure 109. general port pin schematic diagram scanning the reset pin the reset pin accepts 5v active low logic for standard reset operation, and 12v active high logic for high voltage parallel programming. an observe-only cell as shown in fig- ure 110 is inserted both for the 5v reset signal; rstt, and the 12v reset signal; rsthv. figure 110. observe-only cell clk rpx rdx wdx pud synchronizer wdx: write ddrx wrx: write portx rrx: read portx register wpx: write pinx register pud: pullup disable clk : i/o clock rdx: read ddrx d l q q reset q q d q q d clr ddxn pinxn data b u s sleep sleep: sleep control pxn i/o i/o see boundary-scan description for details! puexn ocxn odxn idxn puexn: pullup enable for pin pxn ocxn: output control for pin pxn odxn: output data to pin pxn idxn: input data from pin pxn rpx: read portx pin rrx reset q q d clr portxn wpx 0 1 wrx 0 1 dq from previous cell clockdr shiftdr to next cell from system pin to system logic ff1 239 atmega169v/l 2514j?avr?12/03 scanning the clock pins the avr devices have many clock options selectable by fuses. these are: internal rc oscillator, external clock, (high frequency) crystal oscillator, low-frequency crystal oscillator, and ceramic resonator. figure 111 shows how each oscillator with external connection is supported in the scan chain. the enable signal is supported with a general boundary-scan cell, while the oscillator/clock output is attached to an observe-only cell. in addition to the main clock, the timer oscillator is scanned in the same way. the output from the internal rc oscilla- tor is not scanned, as this oscillator does not have external connections. figure 111. boundary-scan cells for oscillators and clock options table 103 summaries the scan registers for the external clock pin xtal1, oscillators with xtal1/xtal2 connections as well as 32khz timer oscillator. notes: 1. do not enable more than one clock source as main clock at a time. 2. scanning an oscillator output gives unpredictable results as there is a frequency drift between the internal oscillator and the jtag tck clock. if possible, scanning an external clock is preferred. 3. the clock configuration is programmed by fuses. as a fuse is not changed run-time, the clock configuration is considered fixed for a given application. the user is advised to scan the same clock option as to be used in the final system. the enable signals are supported in the scan chain because the system logic can disable clock options in sleep modes, thereby disconnecting the oscillator pins from the scan path if not provided. table 103. scan signals for the oscillator (1)(2)(3) enable signal scanned clock line clock option scanned clock line when not used extclken extclk (xtal1) external clock 0 oscon oscck external crystal external ceramic resonator 1 osc32en osc32ck low freq. external crystal 1 0 1 dq from previous cell clockdr shiftdr to next cell to system logic ff1 0 1 dq dq g 0 1 from previous cell clockdr updatedr shiftdr to next cell extest from digital logic xtal1/tosc1 xtal2/tosc2 oscillator enable output 240 atmega169v/l 2514j?avr?12/03 scanning the analog comparator the relevant comparator signals regarding boundary-scan are shown in figure 112. the boundary-scan cell from figure 113 is attached to each of these signals. the sig- nals are described in table 104. the comparator need not be used for pure connectivity testing, since all analog inputs are shared with a digital port pin as well. figure 112. analog comparator figure 113. general boundary-scan cell used for signals for comparator and adc acbg bandgap reference adc multiplexer output acme ac_idle aco adcen acd 0 1 dq dq g 0 1 from previous cell clockdr updatedr shiftdr to next cell extest to analog circuitry / to digital logic from digital logic/ from analog ciruitry 241 atmega169v/l 2514j?avr?12/03 scanning the adc figure 114 shows a block diagram of the adc with all relevant control and observe sig- nals. the boundary-scan cell from figure 110 is attached to each of these signals. the adc need not be used for pure connectivity testing, since all analog inputs are shared with a digital port pin as well. figure 114. analog to digital converter the signals are described briefly in table 105. table 104. boundary-scan signals for the analog comparator signal name direction as seen from the comparator description recommended input when not in use output values when recommended inputs are used ac_idle input turns off analog comparator when true 1 depends upon c code being executed aco output analog comparator output will become input to c code being executed 0 acme input uses output signal from adc mux when true 0 depends upon c code being executed acbg input bandgap reference enable 0 depends upon c code being executed 10-bit dac + - aref prech dacout comp muxen_7 adc_7 muxen_6 adc_6 muxen_5 adc_5 muxen_4 adc_4 muxen_3 adc_3 muxen_2 adc_2 muxen_1 adc_1 muxen_0 adc_0 negsel_2 adc_2 negsel_1 adc_1 negsel_0 adc_0 extch + - 1x st aclk ampen 1.11v ref irefen aref vccren dac_9..0 adcen hold prech gnden passen comp sctest adcbgen to comparator 1.22v ref acten aref 242 atmega169v/l 2514j?avr?12/03 table 105. boundary-scan signals for the adc (1) signal name direction as seen from the adc description recommen- ded input when not in use output values when recommended inputs are used, and cpu is not using the adc comp output comparator output 0 0 aclk input clock signal to gain stages implemented as switch-cap filters 00 acten input enable path from gain stages to the comparator 00 adcbgen input enable band-gap reference as negative input to comparator 00 adcen input power-on signal to the adc 00 ampen input power-on signal to the gain stages 00 dac_9 input bit 9 of digital value to dac 11 dac_8 input bit 8 of digital value to dac 00 dac_7 input bit 7 of digital value to dac 00 dac_6 input bit 6 of digital value to dac 00 dac_5 input bit 5 of digital value to dac 00 dac_4 input bit 4 of digital value to dac 00 dac_3 input bit 3 of digital value to dac 00 dac_2 input bit 2 of digital value to dac 00 dac_1 input bit 1 of digital value to dac 00 dac_0 input bit 0 of digital value to dac 00 extch input connect adc channels 0 - 3 to by- pass path around gain stages 11 gnden input ground the negative input to comparator when true 00 243 atmega169v/l 2514j?avr?12/03 hold input sample & hold signal. sample analog signal when low. hold signal when high. if gain stages are used, this signal must go active when aclk is high. 11 irefen input enables band-gap reference as aref signal to dac 00 muxen_7 input input mux bit 7 0 0 muxen_6 input input mux bit 6 0 0 muxen_5 input input mux bit 5 0 0 muxen_4 input input mux bit 4 0 0 muxen_3 input input mux bit 3 0 0 muxen_2 input input mux bit 2 0 0 muxen_1 input input mux bit 1 0 0 muxen_0 input input mux bit 0 1 1 negsel_2 input input mux for negative input for differential signal, bit 2 00 negsel_1 input input mux for negative input for differential signal, bit 1 00 negsel_0 input input mux for negative input for differential signal, bit 0 00 passen input enable pass-gate of gain stages. 11 prech input precharge output latch of comparator. (active low) 11 table 105. boundary-scan signals for the adc (1) (continued) signal name direction as seen from the adc description recommen- ded input when not in use output values when recommended inputs are used, and cpu is not using the adc 244 atmega169v/l 2514j?avr?12/03 note: 1. incorrect setting of the switches in figure 114 will make signal contention and may damage the part. there are several input choices to the s&h circuitry on the negative input of the output comparator in figure 114. make sure only one path is selected from either one adc pin, bandgap reference source, or ground. if the adc is not to be used during scan, the recommended input values from table 105 should be used. the user is recommended not to use the differential gain stages dur- ing scan. switch-cap based gain stages require fast operation and accurate timing which is difficult to obtain when used in a scan chain. details concerning operations of the differential gain stage is therefore not provided. the avr adc is based on the analog circuitry shown in figure 114 with a successive approximation algorithm implemented in the digital logic. when used in boundary-scan, the problem is usually to ensure that an applied analog voltage is measured within some limits. this can easily be done without running a successive approximation algorithm: apply the lower limit on the digital dac[9:0] lines, make sure the output from the com- parator is low, then apply the upper limit on the digital dac[9:0] lines, and verify the output from the comparator to be high. the adc need not be used for pure connectivity testing, since all analog inputs are shared with a digital port pin as well. when using the adc, remember the following the port pin for the adc channel in use must be configured to be an input with pull- up disabled to avoid signal contention. in normal mode, a dummy conversion (consisting of 10 comparisons) is performed when enabling the adc. the user is advised to wait at least 200ns after enabling the adc before controlling/observing any adc signal, or perform a dummy conversion before using the first result. the dac values must be stable at the midpoint value 0x200 when having the hold signal low (sample mode). as an example, consider the task of verifying a 1.5v 5% input signal at adc channel 3 when the power supply is 5.0v and aref is externally connected to v cc . sctest input switch-cap test enable. output from x10 gain stage send out to port pin having adc_4 00 st input output of gain stages will settle faster if this signal is high first two aclk periods after ampen goes high. 00 vccren input selects vcc as the acc reference voltage. 00 table 105. boundary-scan signals for the adc (1) (continued) signal name direction as seen from the adc description recommen- ded input when not in use output values when recommended inputs are used, and cpu is not using the adc the lower limit is: 1024 1.5 v 0,95 5 v ? ?? 291 0x123 == the upper limit is: 1024 1.5 v 1.05 5 v ? ?? 323 0x143 == 245 atmega169v/l 2514j?avr?12/03 the recommended values from table 105 are used unless other values are given in the algorithm in table 106. only the dac and port pin values of the scan chain are shown. the column ?actions? describes what jtag instruction to be used before filling the boundary-scan register with the succeeding columns. the verification should be done on the data scanned out when scanning in the data on the same row in the table. using this algorithm, the timing constraint on the hold signal constrains the tck clock frequency. as the algorithm keeps hold high for five steps, the tck clock frequency has to be at least five times the number of scan bits divided by the maximum hold time, t hold,max table 106. algorithm for using the adc step actions adcen dac muxen hold prech pa3. data pa 3 . control pa 3 . pull- up_ enable 1 sample_ preload 1 0x200 0x08 1 1 0 0 0 2 extest 1 0x200 0x08 0 1 0 0 0 3 1 0x200 0x08 1 1 0 0 0 4 1 0x123 0x08 1 1 0 0 0 5 1 0x123 0x08 1 0 0 0 0 6 verify the comp bit scanned out to be 0 1 0x200 0x08 1 1 0 0 0 7 1 0x200 0x08 0 1 0 0 0 8 1 0x200 0x08 1 1 0 0 0 9 1 0x143 0x08 1 1 0 0 0 10 1 0x143 0x08 1 0 0 0 0 11 verify the comp bit scanned out to be 1 1 0x200 0x08 1 1 0 0 0 246 atmega169v/l 2514j?avr?12/03 atmega169 boundary- scan order table 107 shows the scan order between tdi and tdo when the boundary-scan chain is selected as data path. bit 0 is the lsb; the first bit scanned in, and the first bit scanned out. the scan order follows the pin-out order as far as possible. therefore, the bits of port a is scanned in the opposite bit order of the other ports. exceptions from the rules are the scan chains for the analog circuits, which constitute the most significant bits of the scan chain regardless of which physical pin they are connected to. in figure 108, pxn. data corresponds to ff0, pxn. control corresponds to ff1, and pxn. pull- up_enable corresponds to ff2. bit 2, 3, 4, and 5 of port c is not in the scan chain, since these pins constitute the tap pins when the jtag is enabled. table 107. atmega169 boundary-scan order bit number signal name module 197 ac_idle comparator 196 aco 195 acme 194 ainbg 193 comp adc 192 aclk 191 acten 190 private_signal1 (1) 189 adcbgen 188 adcen 187 ampen 186 dac_9 185 dac_8 184 dac_7 183 dac_6 182 dac_5 181 dac_4 180 dac_3 179 dac_2 178 dac_1 177 dac_0 176 extch 175 gnden 174 hold 173 irefen 172 muxen_7 171 muxen_6 170 muxen_5 169 muxen_4 247 atmega169v/l 2514j?avr?12/03 168 muxen_3 adc 167 muxen_2 166 muxen_1 165 muxen_0 164 negsel_2 163 negsel_1 162 negsel_0 161 passen 160 prech 159 st 158 vccren 157 pe0.data port e 156 pe0.control 155 pe0.pull-up_enable 154 pe1.data 153 pe1.control 152 pe1.pull-up_enable 151 pe2.data 150 pe2.control 149 pe2.pull-up_enable 148 pe3.data 147 pe3.control 146 pe3.pull-up_enable 145 pe4.data 144 pe4.control 143 pe4.pull-up_enable 142 pe5.data 141 pe5.control 140 pe5.pull-up_enable 139 pe6.data 138 pe6.control 137 pe6.pull-up_enable 136 pe7.data 135 pe7.control 134 pe7.pull-up_enable 133 pb0.data port b table 107. atmega169 boundary-scan order (continued) bit number signal name module 248 atmega169v/l 2514j?avr?12/03 132 pb0.control port b 131 pb0.pull-up_enable 130 pb1.data 129 pb1.control 128 pb1.pull-up_enable 127 pb2.data 126 pb2.control 125 pb2.pull-up_enable 124 pb3.data 123 pb3.control 122 pb3.pull-up_enable 121 pb4.data 120 pb4.control 119 pb4.pull-up_enable 118 pb5.data 117 pb5.control 116 pb5.pull-up_enable 115 pb6.data 114 pb6.control 113 pb6.pull-up_enable 112 pb7.data 111 pb7.control 110 pb7.pull-up_enable 109 pg3.data port g 108 pg3.control 107 pg3.pull-up_enable 106 pg4.data 105 pg4.control 104 pg4.pull-up_enable 103 pg5 (observe only) 102 rstt reset logic (observe-only) 101 rsthv 100 extclken enable signals for main clock/oscillators 99 oscon 98 rcoscen 97 osc32en table 107. atmega169 boundary-scan order (continued) bit number signal name module 249 atmega169v/l 2514j?avr?12/03 96 extclk (xtal1) clock input and oscillators for the main clock (observe-only) 95 oscck 94 rcck 93 osc32ck 92 pd0.data port d 91 pd0.control 90 pd0.pull-up_enable 89 pd1.data 88 pd1.control 87 pd1.pull-up_enable 86 pd2.data 85 pd2.control 84 pd2.pull-up_enable 83 pd3.data 82 pd3.control 81 pd3.pull-up_enable 80 pd4.data 79 pd4.control 78 pd4.pull-up_enable 77 pd5.data 76 pd5.control 75 pd5.pull-up_enable 74 pd6.data 73 pd6.control 72 pd6.pull-up_enable 71 pd7.data 70 pd7.control 69 pd7.pull-up_enable 68 pg0.data port g 67 pg0.control 66 pg0.pull-up_enable 65 pg1.data 64 pg1.control 63 pg1.pull-up_enable 62 pc0.data port c 61 pc0.control table 107. atmega169 boundary-scan order (continued) bit number signal name module 250 atmega169v/l 2514j?avr?12/03 60 pc0.pull-up_enable port c 59 pc1.data 58 pc1.control 57 pc1.pull-up_enable 56 pc2.data 55 pc2.control 54 pc2.pull-up_enable 53 pc3.data 52 pc3.control 51 pc3.pull-up_enable 50 pc4.data 49 pc4.control 48 pc4.pull-up_enable 47 pc5.data 46 pc5.control 45 pc5.pull-up_enable 44 pc6.data 43 pc6.control 42 pc6.pull-up_enable 41 pc7.data 40 pc7.control 39 pc7.pull-up_enable 38 pg2.data port g 37 pg2.control 36 pg2.pull-up_enable 35 pa7.data port a 34 pa7.control 33 pa7.pull-up_enable 32 pa6.data 31 pa6.control 30 pa6.pull-up_enable 29 pa5.data 28 pa5.control 27 pa5.pull-up_enable 26 pa4.data 25 pa4.control table 107. atmega169 boundary-scan order (continued) bit number signal name module 251 atmega169v/l 2514j?avr?12/03 note: 1. private_signal1 should always be scanned in as zero. boundary-scan description language files boundary-scan description language (bsdl) files describe boundary-scan capable devices in a standard format used by automated test-generation software. the order and function of bits in the boundary-scan data register are included in this description. a bsdl file for atmega169 is available. 24 pa4.pull-up_enable port a 23 pa3.data 22 pa3.control 21 pa3.pull-up_enable 20 pa2.data 19 pa2.control 18 pa2.pull-up_enable 17 pa1.data 16 pa1.control 15 pa1.pull-up_enable 14 pa0.data 13 pa0.control 12 pa0.pull-up_enable 11 pf3.data port f 10 pf3.control 9 pf3.pull-up_enable 8pf2.data 7 pf2.control 6 pf2.pull-up_enable 5pf1.data 4 pf1.control 3 pf1.pull-up_enable 2pf0.data 1 pf0.control 0 pf0.pull-up_enable table 107. atmega169 boundary-scan order (continued) bit number signal name module 252 atmega169v/l 2514j?avr?12/03 boot loader support ? read-while-write self-programming the boot loader support provides a real read-while-write self-programming mecha- nism for downloading and uploading program code by the mcu itself. this feature allows flexible application software updates controlled by the mcu using a flash-resi- dent boot loader program. the boot loader program can use any available data interface and associated protocol to read code and write (program) that code into the flash memory, or read the code from the program memory. the program code within the boot loader section has the capability to write into the entire flash, including the boot loader memory. the boot loader can thus even modify itself, and it can also erase itself from the code if the feature is not needed anymore. the size of the boot loader memory is configurable with fuses and the boot loader has two separate sets of boot lock bits which can be set independently. this gives the user a unique flexibility to select different levels of protection. boot loader features read-while-write self-programming flexible boot memory size high security (separate boot lock bits for a flexible protection) separate fuse to select reset vector optimized page (1) size code efficient algorithm efficient read-modify-write support note: 1. a page is a section in the flash consisting of several bytes (see table 125 on page 272) used during programming. the page organization does not affect normal operation. application and boot loader flash sections the flash memory is organized in two main sections, the application section and the boot loader section (see figure 116). the size of the different sections is configured by the bootsz fuses as shown in table 113 on page 264 and figure 116. these two sections can have different level of protection since they have different sets of lock bits. application section the application section is the section of the flash that is used for storing the application code. the protection level for the application section can be selected by the application boot lock bits (boot lock bits 0), see table 109 on page 256. the application section can never store any boot loader code since the spm instruction is disabled when exe- cuted from the application section. bls ? boot loader section while the application section is used for storing the application code, the the boot loader software must be located in the bls since the spm instruction can initiate a pro- gramming when executing from the bls only. the spm instruction can access the entire flash, including the bls itself. the protection level for the boot loader section can be selected by the boot loader lock bits (boot lock bits 1), see table 110 on page 256. read-while-write and no read-while-write flash sections whether the cpu supports read-while-write or if the cpu is halted during a boot loader software update is dependent on which address that is being programmed. in addition to the two sections that are configurable by the bootsz fuses as described above, the flash is also divided into two fixed sections, the read-while-write (rww) section and the no read-while-write (nrww) section. the limit between the rww- and nrww sections is given in table 114 on page 264 and figure 116 on page 255. the main difference between the two sections is: when erasing or writing a page located inside the rww section, the nrww section can be read during the operation. when erasing or writing a page located inside the nrww section, the cpu is halted during the entire operation. 253 atmega169v/l 2514j?avr?12/03 note that the user software can never read any code that is located inside the rww section during a boot loader software operation. the syntax ?read-while-write sec- tion? refers to which section that is being programmed (erased or written), not which section that actually is being read during a boot loader software update. rww ? read-while-write section if a boot loader software update is programming a page inside the rww section, it is possible to read code from the flash, but only code that is located in the nrww sec- tion. during an on-going programming, the software must ensure that the rww section never is being read. if the user software is trying to read code that is located inside the rww section (i.e., by a call/jmp/lpm or an interrupt) during programming, the software might end up in an unknown state. to avoid this, the interrupts should either be disabled or moved to the boot loader section. the boot loader section is always located in the nrww section. the rww section busy bit (rwwsb) in the store program memory control and status register (spmcsr) will be read as logical one as long as the rww section is blocked for reading. after a programming is completed, the rwwsb must be cleared by software before reading code located in the rww section. see ?store pro- gram memory control and status register ? spmcsr? on page 257. for details on how to clear rwwsb. nrww ? no read-while-write section the code located in the nrww section can be read when the boot loader software is updating a page in the rww section. when the boot loader code updates the nrww section, the cpu is halted during the entire page erase or page write operation. table 108. read-while-write features which section does the z- pointer address during the programming? which section can be read during programming? is the cpu halted? read-while-write supported? rww section nrww section no yes nrww section none yes no 254 atmega169v/l 2514j?avr?12/03 figure 115. read-while-write vs. no read-while-write read-while-write (rww) section no read-while-write (nrww) section z-pointer addresses rww section z-pointer addresses nrww section cpu is halted during the operation code located in nrww section can be read during the operation 255 atmega169v/l 2514j?avr?12/03 figure 116. memory sections note: 1. the parameters in the figure above are given in table 113 on page 264. boot loader lock bits if no boot loader capability is needed, the entire flash is available for application code. the boot loader has two separate sets of boot lock bits which can be set indepen- dently. this gives the user a unique flexibility to select different levels of protection. the user can select: to protect the entire flash from a software update by the mcu. to protect only the boot loader flash section from a software update by the mcu. to protect only the application flash section from a software update by the mcu. allow software update in the entire flash. see table 109 and table 110 for further details. the boot lock bits can be set in soft- ware and in serial or parallel programming mode, but they can be cleared by a chip erase command only. the general write lock (lock bit mode 2) does not control the programming of the flash memory by spm instruction. similarly, the general read/write lock (lock bit mode 1) does not control reading nor writing by lpm/spm, if it is attempted. 0x0000 flashend program memory bootsz = '11' application flash section boot loader flash section flashend program memory bootsz = '10' 0x0000 program memory bootsz = '01' program memory bootsz = '00' application flash section boot loader flash section 0x0000 flashend application flash section flashend end rww start nrww application flash section boot loader flash section boot loader flash section end rww start nrww end rww start nrww 0x0000 end rww, end application start nrww, start boot loader application flash section application flash section application flash section read-while-write section no read-while-write section read-while-write section no read-while-write section read-while-write section no read-while-write section read-while-write section no read-while-write section end application start boot loader end application start boot loader end application start boot loader 256 atmega169v/l 2514j?avr?12/03 note: 1. ?1? means unprogrammed, ?0? means programmed note: 1. ?1? means unprogrammed, ?0? means programmed entering the boot loader program entering the boot loader takes place by a jump or call from the application program. this may be initiated by a trigger such as a command received via usart, or spi inter- face. alternatively, the boot reset fuse can be programmed so that the reset vector is pointing to the boot flash start address after a reset. in this case, the boot loader is started after a reset. after the application code is loaded, the program can start execut- ing the application code. note that the fuses cannot be changed by the mcu itself. this means that once the boot reset fuse is programmed, the reset vector will always point to the boot loader reset and the fuse can only be changed through the serial or parallel programming interface. note: 1. ?1? means unprogrammed, ?0? means programmed table 109. boot lock bit0 protection modes (application section) (1) blb0 mode blb02 blb01 protection 1 1 1 no restrictions for spm or lpm accessing the application section. 2 1 0 spm is not allowed to write to the application section. 3 0 0 spm is not allowed to write to the application section, and lpm executing from the boot loader section is not allowed to read from the application section. if interrupt vectors are placed in the boot loader section, interrupts are disabled while executing from the application section. 4 0 1 lpm executing from the boot loader section is not allowed to read from the application section. if interrupt vectors are placed in the boot loader section, interrupts are disabled while executing from the application section. table 110. boot lock bit1 protection modes (boot loader section) (1) blb1 mode blb12 blb11 protection 1 1 1 no restrictions for spm or lpm accessing the boot loader section. 2 1 0 spm is not allowed to write to the boot loader section. 3 0 0 spm is not allowed to write to the boot loader section, and lpm executing from the application section is not allowed to read from the boot loader section. if interrupt vectors are placed in the application section, interrupts are disabled while executing from the boot loader section. 4 0 1 lpm executing from the application section is not allowed to read from the boot loader section. if interrupt vectors are placed in the application section, interrupts are disabled while executing from the boot loader section. table 111. boot reset fuse (1) bootrst reset address 1 reset vector = application reset (address 0x0000) 0 reset vector = boot loader reset (see table 113 on page 264) 257 atmega169v/l 2514j?avr?12/03 store program memory control and status register ? spmcsr the store program memory control and status register contains the control bits needed to control the boot loader operations. bit 7 ? spmie: spm interrupt enable when the spmie bit is written to one, and the i-bit in the status register is set (one), the spm ready interrupt will be enabled. the spm ready interrupt will be executed as long as the spmen bit in the spmcsr register is cleared. bit 6 ? rwwsb: read-while-write section busy when a self-programming (page erase or page write) operation to the rww section is initiated, the rwwsb will be set (one) by hardware. when the rwwsb bit is set, the rww section cannot be accessed. the rwwsb bit will be cleared if the rwwsre bit is written to one after a self-programming operation is completed. alternatively the rwwsb bit will automatically be cleared if a page load operation is initiated. bit 5 ? res: reserved bit this bit is a reserved bit in the atmega169 and always read as zero. bit 4 ? rwwsre: read-while-write section read enable when programming (page erase or page write) to the rww section, the rww section is blocked for reading (the rwwsb will be set by hardware). to re-enable the rww section, the user software must wait until the programming is completed (spmen will be cleared). then, if the rwwsre bit is written to one at the same time as spmen, the next spm instruction within four clock cycles re-enables the rww section. the rww section cannot be re-enabled while the flash is busy with a page erase or a page write (spmen is set). if the rwwsre bit is written while the flash is being loaded, the flash load operation will abort and the data loaded will be lost. bit 3 ? blbset: boot lock bit set if this bit is written to one at the same time as spmen, the next spm instruction within four clock cycles sets boot lock bits, according to the data in r0. the data in r1 and the address in the z-pointer are ignored. the blbset bit will automatically be cleared upon completion of the lock bit set, or if no spm instruction is executed within four clock cycles. an lpm instruction within three cycles after blbset and spmen are set in the spmcsr register, will read either the lock bits or the fuse bits (depending on z0 in the z-pointer) into the destination register. see ?reading the fuse and lock bits from software? on page 261 for details. bit 2 ? pgwrt: page write if this bit is written to one at the same time as spmen, the next spm instruction within four clock cycles executes page write, with the data stored in the temporary buffer. the page address is taken from the high part of the z-pointer. the data in r1 and r0 are ignored. the pgwrt bit will auto-clear upon completion of a page write, or if no spm instruction is executed within four clock cycles. the cpu is halted during the entire page write operation if the nrww section is addressed. bit 7 6 5 4 3 2 1 0 spmie rwwsb ? rwwsre blbset pgwrt pgers spmen spmcsr read/write r/w r r r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 258 atmega169v/l 2514j?avr?12/03 bit 1 ? pgers: page erase if this bit is written to one at the same time as spmen, the next spm instruction within four clock cycles executes page erase. the page address is taken from the high part of the z-pointer. the data in r1 and r0 ar e ignored. the pgers bit will auto-clear upon completion of a page erase, or if no spm instruction is executed within four clock cycles. the cpu is halted during the entire page write operation if the nrww section is addressed. bit 0 ? spmen: store program memory enable this bit enables the spm instruction for the next four clock cycles. if written to one together with either rwwsre, blbset, pgwrt? or pgers, the following spm instruction will have a special meaning, see description above. if only spmen is written, the following spm instruction will store the value in r1:r0 in the temporary page buffer addressed by the z-pointer. the lsb of the z-pointer is ignored. the spmen bit will auto-clear upon completion of an spm instruction, or if no spm instruction is executed within four clock cycles. during page erase and page write, the spmen bit remains high until the operation is completed. writing any other combination than ?10001?, ?01001?, ?00101?, ?00011? or ?00001? in the lower five bits will have no effect. addressing the flash during self- programming the z-pointer is used to address the spm commands. since the flash is organized in pages (see table 125 on page 272), the program counter can be treated as having two different sections. one section, consisting of the least significant bits, is addressing the words within a page, while the most significant bits are addressing the pages. this is shown in figure 117. note that the page erase and page write operations are addressed independently. therefore it is of major impor- tance that the boot loader software addresses the same page in both the page erase and page write operation. once a programming operation is initiated, the address is latched and the z-pointer can be used for other operations. the only spm operation that does not use the z-pointer is setting the boot loader lock bits. the content of the z-pointer is ignored and will have no effect on the operation. the lpm instruction does also use the z-pointer to store the address. since this instruction addresses the flash byte-by-byte, also the lsb (bit z0) of the z-pointer is used. bit 151413121110 9 8 zh (r31) z15 z14 z13 z12 z11 z10 z9 z8 zl (r30) z7z6z5z4z3z2z1z0 76543210 259 atmega169v/l 2514j?avr?12/03 figure 117. addressing the flash during spm (1) note: 1. the different variables used in figure 117 are listed in table 115 on page 265. 2. pcpage and pcword are listed in table 125 on page 272. self-programming the flash the program memory is updated in a page by page fashion. before programming a page with the data stored in the temporary page buffer, the page must be erased. the temporary page buffer is filled one word at a time using spm and the buffer can be filled either before the page erase command or between a page erase and a page write operation: alternative 1, fill the buffer before a page erase fill temporary page buffer perform a page erase perform a page write alternative 2, fill the buffer after page erase perform a page erase fill temporary page buffer perform a page write if only a part of the page needs to be changed, the rest of the page must be stored (for example in the temporary page buffer) before the erase, and then be rewritten. when using alternative 1, the boot loader provides an effective read-modify-write feature which allows the user software to first read the page, do the necessary changes, and then write back the modified data. if alternative 2 is used, it is not possible to read the old data while loading since the page is already erased. the temporary page buffer can be accessed in a random sequence. it is essential that the page address used in both the page erase and page write operation is addressing the same page. see ?simple assembly code example for a boot loader? on page 263 for an assembly code example. program memory 0 1 15 z - register bit 0 zpagemsb word address within a page page address within the flash zpcmsb instruction word pag e pcword[pagemsb:0]: 00 01 02 pageend pag e pcword pcpage pcmsb pagemsb program counter 260 atmega169v/l 2514j?avr?12/03 performing page erase by spm to execute page erase, set up the address in the z-pointer, write ?x0000011? to spmcsr and execute spm within four clock cycles after writing spmcsr. the data in r1 and r0 is ignored. the page address must be written to pcpage in the z-register. other bits in the z-pointer will be ignored during this operation. page erase to the rww section: the nrww section can be read during the page erase. page erase to the nrww section: the cpu is halted during the operation. filling the temporary buffer (page loading) to write an instruction word, set up the address in the z-pointer and data in r1:r0, write ?00000001? to spmcsr and execute spm within four clock cycles after writing spmcsr. the content of pcword in the z-register is used to address the data in the temporary buffer. the temporary buffer will auto-erase after a page write operation or by writing the rwwsre bit in spmcsr. it is also erased after a system reset. note that it is not possible to write more than one time to each address without erasing the tempo- rary buffer. if the eeprom is written in the middle of an spm page load operation, all data loaded will be lost. performing a page write to execute page write, set up the address in the z-pointer, write ?x0000101? to spmcsr and execute spm within four clock cycles after writing spmcsr. the data in r1 and r0 is ignored. the page address must be written to pcpage. other bits in the z-pointer must be written to zero during this operation. page write to the rww section: the nrww section can be read during the page write. page write to the nrww section: the cpu is halted during the operation. using the spm interrupt if the spm interrupt is enabled, the spm interrupt will generate a constant interrupt when the spmen bit in spmcsr is cleared. this means that the interrupt can be used instead of polling the spmcsr register in software. when using the spm interrupt, the interrupt vectors should be moved to the bls section to avoid that an interrupt is accessing the rww section when it is blocked for reading. how to move the interrupts is described in ?interrupts? on page 46. consideration while updating bls special care must be taken if the user allows the boot loader section to be updated by leaving boot lock bit11 unprogrammed. an accidental write to the boot loader itself can corrupt the entire boot loader, and further software updates might be impossible. if it is not necessary to change the boot loader software itself, it is recommended to program the boot lock bit11 to protect the boot loader software from any internal software changes. prevent reading the rww section during self- programming during self-programming (either page erase or page write), the rww section is always blocked for reading. the user software itself must prevent that this section is addressed during the self programming operation. the rwwsb in the spmcsr will be set as long as the rww section is busy. during self-programming the interrupt vector table should be moved to the bls as described in ?interrupts? on page 46, or the inter- rupts must be disabled. before addressing the rww section after the programming is completed, the user software must clear the rwwsb by writing the rwwsre. see ?simple assembly code example for a boot loader? on page 263 for an example. 261 atmega169v/l 2514j?avr?12/03 setting the boot loader lock bits by spm to set the boot loader lock bits, write the desired data to r0, write ?x0001001? to spmcsr and execute spm within four clock cycles after writing spmcsr. the only accessible lock bits are the boot lock bits that may prevent the application and boot loader section from any software update by the mcu. see table 109 and table 110 for how the different settings of the boot loader bits affect the flash access. if bits 5..2 in r0 are cleared (zero), the corresponding boot lock bit will be programmed if an spm instruction is executed within four cycles after blbset and spmen are set in spmcsr. the z-pointer is don?t care during this operation, but for future compatibility it is recommended to load the z-pointer with 0x0001 (same as used for reading the lo ck bits). for future compatibility it is also recommended to set bits 7, 6, 1, and 0 in r0 to ?1? when writing the lock bits. when programming the lock bits the entire flash can be read during the operation. eeprom write prevents writing to spmcsr note that an eeprom write operation will block all software programming to flash. reading the fuses and lock bits from software will also be prevented during the eeprom write operation. it is recommended that the user checks the status bit (eewe) in the eecr register and verifies that the bit is cleared before writing to the spmcsr register. reading the fuse and lock bits from software it is possible to read both the fuse and lock bits from software. to read the lock bits, load the z-pointer with 0x0001 and set the blbset and spmen bits in spmcsr. when an lpm instruction is executed within three cpu cycles after the blbset and spmen bits are set in spmcsr, the value of the lock bits will be loaded in the destina- tion register. the blbset and spmen bits will auto-clear upon completion of reading the lock bits or if no lpm instruction is executed within three cpu cycles or no spm instruction is executed within four cpu cycles. when blbset and spmen are cleared, lpm will work as described in the instruction set manual. the algorithm for reading the fuse low byte is similar to the one described above for reading the lock bits. to read the fuse low byte, load the z-pointer with 0x0000 and set the blbset and spmen bits in spmcsr. when an lpm instruction is executed within three cycles after the blbset and spmen bits are set in the spmcsr, the value of the fuse low byte (flb) will be loaded in the destination register as shown below. refer to table 120 on page 268 for a detailed description and mapping of the fuse low byte. similarly, when reading the fuse high byte, load 0x0003 in the z-pointer. when an lpm instruction is executed within three cycles after the blbset and spmen bits are set in the spmcsr, the value of the fuse high byte (fhb) will be loaded in the destination register as shown below. refer to table 119 on page 268 for detailed description and mapping of the fuse high byte. bit 76543210 r0 1 1 blb12 blb11 blb02 blb01 1 1 bit 76543210 rd ? ? blb12 blb11 blb02 blb01 lb2 lb1 bit 76543210 rd flb7 flb6 flb5 flb4 flb3 flb2 flb1 flb0 bit 76543210 rd fhb7 fhb6 fhb5 fhb4 fhb3 fhb2 fhb1 fhb0 262 atmega169v/l 2514j?avr?12/03 when reading the extended fuse byte, load 0x0002 in the z-pointer. when an lpm instruction is executed within three cycles after the blbset and spmen bits are set in the spmcsr, the value of the extended fuse byte (efb) will be loaded in the destina- tion register as shown below. refer to table 118 on page 267 for detailed description and mapping of the extended fuse byte. fuse and lock bits that are programmed, will be read as zero. fuse and lock bits that are unprogrammed, will be read as one. preventing flash corruption during periods of low v cc , the flash program can be corrupted because the supply volt- age is too low for the cpu and the flash to operate properly. these issues are the same as for board level systems using the flash, and the same design solutions should be applied. a flash program corruption can be caused by two situations when the voltage is too low. first, a regular write sequence to the flash requires a minimum voltage to operate cor- rectly. secondly, the cpu itself can execute instructions incorrectly, if the supply voltage for executing instructions is too low. flash corruption can easily be avoided by following these design recommendations (one is sufficient): 1. if there is no need for a boot loader update in the system, program the boot loader lock bits to prevent any boot loader software updates. 2. keep the avr reset active (low) during periods of insufficient power supply voltage. this can be done by enabling the internal brown-out detector (bod) if the operating voltage matches the detection level. if not, an external low v cc reset protection circuit can be used. if a reset occurs while a write operation is in progress, the write operation will be completed provided that the power supply voltage is sufficient. 3. keep the avr core in power-down sleep mode during periods of low v cc . this will prevent the cpu from attempting to decode and execute instructions, effec- tively protecting the spmcsr register and thus the flash from unintentional writes. programming time for flash when using spm the calibrated rc oscillator is used to time flash accesses. table 112 shows the typi- cal programming time for flash accesses from the cpu. bit 76543210 rd ? ? ? ? efb3 efb2 efb1 efb0 table 112. spm programming time symbol min programming time max programming time flash write (page erase, page write, and write lock bits by spm) 3.7 ms 4.5 ms 263 atmega169v/l 2514j?avr?12/03 simple assembly code example for a boot loader ;-the routine writes one page of data from ram to flash ; the first data location in ram is pointed to by the y pointer ; the first data location in flash is pointed to by the z-pointer ;-error handling is not included ;-the routine must be placed inside the boot space ; (at least the do_spm sub routine). only code inside nrww section can ; be read during self-programming (page erase and page write). ;-registers used: r0, r1, temp1 (r16), temp2 (r17), looplo (r24), ; loophi (r25), spmcrval (r20) ; storing and restoring of registers is not included in the routine ; register usage can be optimized at the expense of code size ;-it is assumed that either the interrupt table is moved to the boot ; loader section or that the interrupts are disabled. .equ pagesizeb = pagesize*2 ;pagesizeb is page size in bytes, not words .org smallbootstart write_page: ; page erase ldi spmcrval, (1< 266 atmega169v/l 2514j?avr?12/03 memory programming program and data memory lock bits the atmega169 provides six lock bits which can be left unprogrammed (?1?) or can be programmed (?0?) to obtain the additional features listed in table 117. the lock bits can only be erased to ?1? with the chip erase command. note: 1. ?1? means unprogrammed, ?0? means programmed table 116. lock bit byte (1) lock bit byte bit no description default value 7 ? 1 (unprogrammed) 6 ? 1 (unprogrammed) blb12 5 boot lock bit 1 (unprogrammed) blb11 4 boot lock bit 1 (unprogrammed) blb02 3 boot lock bit 1 (unprogrammed) blb01 2 boot lock bit 1 (unprogrammed) lb2 1 lock bit 1 (unprogrammed) lb1 0 lock bit 1 (unprogrammed) table 117. lock bit protection modes (1)(2) memory lock bits protection type lb mode lb2 lb1 1 1 1 no memory lock features enabled. 210 further programming of the flash and eeprom is disabled in parallel and serial programming mode. the fuse bits are locked in both serial and parallel programming mode. (1) 300 further programming and verification of the flash and eeprom is disabled in parallel and serial programming mode. the boot lock bits and fuse bits are locked in both serial and parallel programming mode. (1) blb0 mode blb02 blb01 111 no restrictions for spm or lpm accessing the application section. 2 1 0 spm is not allowed to write to the application section. 300 spm is not allowed to write to the application section, and lpm executing from the boot loader section is not allowed to read from the application section. if interrupt vectors are placed in the boot loader section, interrupts are disabled while executing from the application section. 401 lpm executing from the boot loader section is not allowed to read from the application section. if interrupt vectors are placed in the boot loader section, interrupts are disabled while executing from the application section. blb1 mode blb12 blb11 267 atmega169v/l 2514j?avr?12/03 notes: 1. program the fuse bits and boot lock bits before programming the lb1 and lb2. 2. ?1? means unprogrammed, ?0? means programmed fuse bits the atmega169 has three fuse bytes. table 118 - table 120 describe briefly the func- tionality of all the fuses and how they are mapped into the fuse bytes. note that the fuses are read as logical zero, ?0?, if they are programmed. notes: 1. see table 17 on page 39 for bodl evel fuse decoding. 111 no restrictions for spm or lpm accessing the boot loader section. 2 1 0 spm is not allowed to write to the boot loader section. 300 spm is not allowed to write to the boot loader section, and lpm executing from the application section is not allowed to read from the boot loader section. if interrupt vectors are placed in the application section, interrupts are disabled while executing from the boot loader section. 401 lpm executing from the application section is not allowed to read from the boot loader section. if interrupt vectors are placed in the application section, interrupts are disabled while executing from the boot loader section. table 117. lock bit protection modes (1)(2) (continued) memory lock bits protection type table 118. extended fuse byte fuse low byte bit no description default value ?7? 1 ?6? 1 ?5? 1 ?4? 1 bodlevel2 (1) 3 brown-out detector trigger level 1 (unprogrammed) bodlevel1 (1) 2 brown-out detector trigger level 1 (unprogrammed) bodlevel0 (1) 1 brown-out detector trigger level 1 (unprogrammed) 268 atmega169v/l 2514j?avr?12/03 note: 1. the spien fuse is not accessible in serial programming mode. 2. the default value of bootsz1..0 results in maximum boot size. see table 121 on page 271 for details. 3. see ?watchdog timer control register ? wdtcr? on page 43 for details. 4. never ship a product with the ocden fuse programmed regardless of the setting of lock bits and jtagen fuse. a programmed ocden fuse enables some parts of the clock system to be running in all sleep modes. this may increase the power consumption. 5. if the jtag interface is left unconnected, the jtagen fuse should if possible be dis- abled. this to avoid static current at the tdo pin in the jtag interface. note: 1. the default value of sut1..0 results in maximum start-up time for the default clock source. see table 16 on page 37 for details. 2. the default setting of cksel3..0 results in internal rc oscillator @ 8 mhz. see table 6 on page 26 for details. 3. the ckout fuse allow the system clock to be output on porte7. see ?clock out- put buffer? on page 29 for details. 4. see ?system clock prescaler? on page 30 for details. table 119. fuse high byte fuse high byte bit no description default value ocden (4) 7 enable ocd 1 (unprogrammed, ocd disabled) jtagen (5) 6 enable jtag 0 (programmed, jtag enabled) spien (1) 5 enable serial program and data downloading 0 (programmed, spi prog. enabled) wdton (3) 4 watchdog timer always on 1 (unprogrammed) eesave 3 eeprom memory is preserved through the chip erase 1 (unprogrammed, eeprom not preserved) bootsz1 2 select boot size (see table 121 for details) 0 (programmed) (2) bootsz0 1 select boot size (see table 121 for details) 0 (programmed) (2) bootrst 0 select reset vector 1 (unprogrammed) table 120. fuse low byte fuse low byte bit no description default value ckdiv8 (4) 7 divide clock by 8 0 (programmed) ckout (3) 6 clock output 1 (unprogrammed) sut1 5 select start-up time 1 (unprogrammed) (1) sut0 4 select start-up time 0 (programmed) (1) cksel3 3 select clock source 0 (programmed) (2) cksel2 2 select clock source 0 (programmed) (2) cksel1 1 select clock source 1 (unprogrammed) (2) cksel0 0 select clock source 0 (programmed) (2) 269 atmega169v/l 2514j?avr?12/03 the status of the fuse bits is not affected by chip erase. note that the fuse bits are locked if lock bit1 (lb1) is programmed. program the fuse bits before programming the lock bits. 270 atmega169v/l 2514j?avr?12/03 latching of fuses the fuse values are latched when the device enters programming mode and changes of the fuse values will have no effect until the part leaves programming mode. this does not apply to the eesave fuse which will take effect once it is programmed. the fuses are also latched on power-up in normal mode. signature bytes all atmel microcontrollers have a three-byte signature code which identifies the device. this code can be read in both serial and parallel mode, also when the device is locked. the three bytes reside in a separate address space. for the atmega169 the signature bytes are: 1. 0x000: 0x1e (indicates manufactured by atmel). 2. 0x001: 0x94 (indicates 16kb flash memory). 3. 0x002: 0x05 (indicates atmega169 device when 0x001 is 0x94). calibration byte the atmega169 has a byte calibration value for the internal rc oscillator. this byte resides in the high byte of address 0x000 in the signature address space. during reset, this byte is automatically written into the osccal register to ensure correct frequency of the calibrated rc oscillator. parallel programming parameters, pin mapping, and commands this section describes how to parallel program and verify flash program memory, eeprom data memory, memory lock bits, and fuse bits in the atmega169. pulses are assumed to be at least 250 ns unless otherwise noted. signal names in this section, some pins of the atmega169 are referenced by signal names describing their functionality during parallel programming, see figure 118 and table 121. pins not described in the following table are referenced by pin names. the xa1/xa0 pins determine the action executed when the xtal1 pin is given a posi- tive pulse. the bit coding is shown in table 123. when pulsing wr or oe , the command loaded determines the action executed. the dif- ferent commands are shown in table 124. figure 118. parallel programming vcc +5v gnd xtal1 pd1 pd2 pd3 pd4 pd5 pd6 pb7 - pb0 data reset pd7 +12 v bs1 xa0 xa1 oe rdy/bsy pagel pa0 wr bs2 avcc +5v 271 atmega169v/l 2514j?avr?12/03 table 121. pin name mapping signal name in programming mode pin name i/o function rdy/bsy pd1 o 0: device is busy programming, 1: device is ready for new command. oe pd2 i output enable (active low). wr pd3 i write pulse (active low). bs1 pd4 i byte select 1 (?0? selects low byte, ?1? selects high byte). xa0 pd5 i xtal action bit 0 xa1 pd6 i xtal action bit 1 pagel pd7 i program memory and eeprom data page load. bs2 pa0 i byte select 2 (?0? selects low byte, ?1? selects 2?nd high byte). data pb7-0 i/o bi-directional data bus (output when oe is low). table 122. pin values used to enter programming mode pin symbol value pagel prog_enable[3] 0 xa1 prog_enable[2] 0 xa0 prog_enable[1] 0 bs1 prog_enable[0] 0 table 123. xa1 and xa0 coding xa1 xa0 action when xtal1 is pulsed 0 0 load flash or eeprom address (high or low address byte determined by bs1). 0 1 load data (high or low data byte for flash determined by bs1). 1 0 load command 1 1 no action, idle 272 atmega169v/l 2514j?avr?12/03 serial programming pin mapping table 124. command byte bit coding command byte command executed 1000 0000 chip erase 0100 0000 write fuse bits 0010 0000 write lock bits 0001 0000 write flash 0001 0001 write eeprom 0000 1000 read signature bytes and calibration byte 0000 0100 read fuse and lock bits 0000 0010 read flash 0000 0011 read eeprom table 125. no. of words in a page and no. of pages in the flash flash size page size pcword no. of pages pcpage pcmsb 8k words (16k bytes) 64 words pc[5:0] 128 pc[12:6] 12 table 126. no. of words in a page and no. of pages in the eeprom eeprom size page size pcword no. of pages pcpage eeamsb 512 bytes 4 bytes eea[1:0] 128 eea[8:2] 8 table 127. pin mapping serial programming symbol pins i/o description mosi pb2 i serial data in miso pb3 o serial data out sck pb1 i serial clock 273 atmega169v/l 2514j?avr?12/03 parallel programming enter programming mode the following algorithm puts the device in parallel programming mode: 1. apply 4.5 - 5.5v between v cc and gnd. 2. set reset to ?0? and toggle xtal1 at least six times. 3. set the prog_enable pins listed in table 122 on page 271 to ?0000? and wait at least 100 ns. 4. apply 11.5 - 12.5v to reset . any activity on prog_enable pins within 100 ns after +12v has been applied to reset , will cause the device to fail entering pro- gramming mode. 5. wait at least 50 s before sending a new command. considerations for efficient programming the loaded command and address are retained in the device during programming. for efficient programming, the following should be considered. the command needs only be loaded once when writing or reading multiple memory locations. skip writing the data value 0xff, that is the contents of the entire eeprom (unless the eesave fuse is programmed) and flash after a chip erase. address high byte needs only be loaded before programming or reading a new 256 word window in flash or 256 byte eeprom. this consideration also applies to signature bytes reading. chip erase the chip erase will erase the flash and eeprom (1) memories plus lock bits. the lock bits are not reset until the program memory has been completely erased. the fuse bits are not changed. a chip erase must be performed before the flash and/or eeprom are reprogrammed. note: 1. the eeprpom memory is preserved during chip erase if the eesave fuse is programmed. load command ?chip erase? 1. set xa1, xa0 to ?10?. this enables command loading. 2. set bs1 to ?0?. 3. set data to ?1000 0000?. this is the command for chip erase. 4. give xtal1 a positive pulse. this loads the command. 5. give wr a negative pulse. this starts the chip erase. rdy/bsy goes low. 6. wait until rdy/bsy goes high before loading a new command. programming the flash the flash is organized in pages, see table 125 on page 272. when programming the flash, the program data is latched into a page buffer. this allows one page of program data to be programmed simultaneously. the following procedure describes how to pro- gram the entire flash memory: a. load command ?write flash? 1. set xa1, xa0 to ?10?. this enables command loading. 2. set bs1 to ?0?. 3. set data to ?0001 0000?. this is the command for write flash. 4. give xtal1 a positive pulse. this loads the command. b. load address low byte 274 atmega169v/l 2514j?avr?12/03 1. set xa1, xa0 to ?00?. this enables address loading. 2. set bs1 to ?0?. this selects low address. 3. set data = address low byte (0x00 - 0xff). 4. give xtal1 a positive pulse. this loads the address low byte. c. load data low byte 1. set xa1, xa0 to ?01?. this enables data loading. 2. set data = data low byte (0x00 - 0xff). 3. give xtal1 a positive pulse. this loads the data byte. d. load data high byte 1. set bs1 to ?1?. this selects high data byte. 2. set xa1, xa0 to ?01?. this enables data loading. 3. set data = data high byte (0x00 - 0xff). 4. give xtal1 a positive pulse. this loads the data byte. e. latch data 1. set bs1 to ?1?. this selects high data byte. 2. give pagel a positive pulse. this latches the data bytes. (see figure 120 for signal waveforms) f. repeat b through e until the entire buffer is filled or until all data within the page is loaded. while the lower bits in the address are mapped to words within the page, the higher bits address the pages within the flash. this is illustrated in figure 119 on page 275. note that if less than eight bits are required to address words in the page (pagesize < 256), the most significant bit(s) in the address low byte are used to address the page when performing a page write. g. load address high byte 1. set xa1, xa0 to ?00?. this enables address loading. 2. set bs1 to ?1?. this selects high address. 3. set data = address high byte (0x00 - 0xff). 4. give xtal1 a positive pulse. this loads the address high byte. h. program page 1. give wr a negative pulse. this starts programming of the entire page of data. rdy/bsy goes low. 2. wait until rdy/bsy goes high (see figure 120 for signal waveforms). i. repeat b through h until the entire flash is programmed or until all data has been programmed. j. end page programming 1. 1. set xa1, xa0 to ?10?. this enables command loading. 2. set data to ?0000 0000?. this is the command for no operation. 3. give xtal1 a positive pulse. this loads the command, and the internal write sig- nals are reset. 275 atmega169v/l 2514j?avr?12/03 figure 119. addressing the flash which is organized in pages (1) note: 1. pcpage and pcword are listed in table 125 on page 272. figure 120. programming the flash waveforms (1) note: 1. ?xx? is don?t care. the letters refer to the programming description above. programming the eeprom the eeprom is organized in pages, see table 126 on page 272. when programming the eeprom, the program data is latched into a page buffer. this allows one page of data to be programmed simultaneously. the programming algorithm for the eeprom data memory is as follows (refer to ?programming the flash? on page 273 for details on command, address and data loading): 1. a: load command ?0001 0001?. 2. g: load address high byte (0x00 - 0xff). 3. b: load address low byte (0x00 - 0xff). 4. c: load data (0x00 - 0xff). 5. e: latch data (give pagel a positive pulse). program memory word address within a page page address within the flash instruction word pag e pcword[pagemsb:0]: 00 01 02 pageend pag e pcword pcpage pcmsb pagemsb program counter rdy/bsy wr oe reset +12v pagel bs2 0x10 addr. low addr. high data data low data high addr. low data low data high xa1 xa0 bs1 xtal1 xx xx xx abcdeb cdegh f 276 atmega169v/l 2514j?avr?12/03 k: repeat 3 through 5 until the entire buffer is filled. l: program eeprom page 1. set bs to ?0?. 2. give wr a negative pulse. this starts programming of the eeprom page. rdy/bsy goes low. 3. wait until to rdy/bsy goes high before programming the next page (see figure 121 for signal waveforms). figure 121. programming the eeprom waveforms reading the flash the algorithm for reading the flash memory is as follows (refer to ?programming the flash? on page 273 for details on command and address loading): 1. a: load command ?0000 0010?. 2. g: load address high byte (0x00 - 0xff). 3. b: load address low byte (0x00 - 0xff). 4. set oe to ?0?, and bs1 to ?0?. the flash word low byte can now be read at data. 5. set bs to ?1?. the flash word high byte can now be read at data. 6. set oe to ?1?. reading the eeprom the algorithm for reading the eeprom memory is as follows (refer to ?programming the flash? on page 273 for details on command and address loading): 1. a: load command ?0000 0011?. 2. g: load address high byte (0x00 - 0xff). 3. b: load address low byte (0x00 - 0xff). 4. set oe to ?0?, and bs1 to ?0?. the eeprom data byte can now be read at data. 5. set oe to ?1?. rdy/bsy wr oe reset +12v pagel bs2 0x11 addr. high data addr. low data addr. low data xx xa1 xa0 bs1 xtal1 xx agbceb c el k 277 atmega169v/l 2514j?avr?12/03 programming the fuse low bits the algorithm for programming the fuse low bi ts is as follows (refer to ?programming the flash? on page 273 for details on command and data loading): 1. a: load command ?0100 0000?. 2. c: load data low byte. bit n = ?0? programs and bit n = ?1? erases the fuse bit. 3. give wr a negative pulse and wait for rdy/bsy to go high. programming the fuse high bits the algorithm for programming the fuse high bits is as follows (refer to ?programming the flash? on page 273 for details on command and data loading): 1. a: load command ?0100 0000?. 2. c: load data low byte. bit n = ?0? programs and bit n = ?1? erases the fuse bit. 3. set bs1 to ?1? and bs2 to ?0?. this selects high data byte. 4. give wr a negative pulse and wait for rdy/bsy to go high. 5. set bs1 to ?0?. this selects low data byte. programming the extended fuse bits the algorithm for programming the extended fuse bits is as follows (refer to ?program- ming the flash? on page 273 for details on command and data loading): 1. 1. a: load command ?0100 0000?. 2. 2. c: load data low byte. bit n = ?0? programs and bit n = ?1? erases the fuse bit. 3. 3. set bs1 to ?0? and bs2 to ?1?. this selects extended data byte. 4. 4. give wr a negative pulse and wait for rdy/bsy to go high. 5. 5. set bs2 to ?0?. this selects low data byte. figure 122. programming the fuses waveforms programming the lock bits the algorithm for programming the lock bits is as follows (refer to ?programming the flash? on page 273 for details on command and data loading): 1. a: load command ?0010 0000?. 2. c: load data low byte. bit n = ?0? programs the lock bit. if lb mode 3 is pro- grammed (lb1 and lb2 is programmed), it is not possible to program the boot lock bits by any external programming mode. 3. give wr a negative pulse and wait for rdy/bsy to go high. the lock bits can only be cleared by executing chip erase. rdy/bsy wr oe reset +12v pagel 0x40 data data xx xa1 xa0 bs1 xtal1 ac 0x40 data xx ac write fuse low byte write fuse high byte 0x40 data xx ac write extended fuse byte bs2 278 atmega169v/l 2514j?avr?12/03 reading the fuse and lock bits the algorithm for reading the fuse and lock bits is as follows (refer to ?programming the flash? on page 273 for details on command loading): 1. a: load command ?0000 0100?. 2. set oe to ?0?, bs2 to ?0? and bs1 to ?0?. the status of the fuse low bits can now be read at data (?0? means programmed). 3. set oe to ?0?, bs2 to ?1? and bs1 to ?1?. the status of the fuse high bits can now be read at data (?0? means programmed). 4. set oe to ?0?, bs2 to ?1?, and bs1 to ?0?. the status of the extended fuse bits can now be read at data (?0? means programmed). 5. set oe to ?0?, bs2 to ?0? and bs1 to ?1?. the status of the lock bits can now be read at data (?0? means programmed). 6. set oe to ?1?. figure 123. mapping between bs1, bs2 and the fuse and lock bits during read reading the signature bytes the algorithm for reading the signature bytes is as follows (refer to ?programming the flash? on page 273 for details on command and address loading): 1. a: load command ?0000 1000?. 2. b: load address low byte (0x00 - 0x02). 3. set oe to ?0?, and bs to ?0?. the selected signature byte can now be read at data. 4. set oe to ?1?. reading the calibration byte the algorithm for reading the calibration byte is as follows (refer to ?programming the flash? on page 273 for details on command and address loading): 1. a: load command ?0000 1000?. 2. b: load address low byte, 0x00. 3. set oe to ?0?, and bs1 to ?1?. the calibration byte can now be read at data. 4. set oe to ?1?. lock bits 0 1 bs2 fuse high byte 0 1 bs1 data fuse low byte 0 1 bs2 extended fuse byte 279 atmega169v/l 2514j?avr?12/03 parallel programming characteristics figure 124. parallel programming timing, including some general timing requirements figure 125. parallel programming timing, loading sequence with timing requirements (1) note: 1. the timing requirements shown in figure 124 (i.e., t dvxh , t xhxl , and t xldx ) also apply to loading operation. data & contol (data, xa0/1, bs1, bs2) xtal1 t xhxl t wlwh t dvxh t xldx t plwl t wlrh wr rdy/bsy pagel t phpl t plbx t bvph t xlwl t wlbx t bvwl wlrl xtal1 pagel t plxh xlxh t t xlph addr0 (low byte) data (low byte) data (high byte) addr1 (low byte) data bs1 xa0 xa1 load address (low byte) load data (low byte) load data (high byte) load data load address (low byte) 280 atmega169v/l 2514j?avr?12/03 figure 126. parallel programming timing, reading sequence (within the same page) with timing requirements (1) note: 1. the timing requirements shown in figure 124 (i.e., t dvxh , t xhxl , and t xldx ) also apply to reading operation. table 128. parallel programming characteristics, v cc = 5v 10% symbol parameter min typ max units v pp programming enable voltage 11.5 12.5 v i pp programming enable current 250 a t dvxh data and control valid before xtal1 high 67 ns t xlxh xtal1 low to xtal1 high 200 ns t xhxl xtal1 pulse width high 150 ns t xldx data and control hold after xtal1 low 67 ns t xlwl xtal1 low to wr low 0 ns t xlph xtal1 low to pagel high 0 ns t plxh pagel low to xtal1 high 150 ns t bvph bs1 valid before pagel high 67 ns t phpl pagel pulse width high 150 ns t plbx bs1 hold after pagel low 67 ns t wlbx bs2/1 hold after wr low 67 ns t plwl pagel low to wr low 67 ns t bvwl bs1 valid to wr low 67 ns t wlwh wr pulse width low 150 ns t wlrl wr low to rdy/bsy low 0 1 s t wlrh wr low to rdy/bsy high (1) 3.7 4.5 ms t wlrh_ce wr low to rdy/bsy high for chip erase (2) 7.5 9 ms t xlol xtal1 low to oe low 0 ns xtal1 oe addr0 (low byte) data (low byte) data (high byte) addr1 (low byte) data bs1 xa0 xa1 load address (low byte) read data (low byte) read data (high byte) load address (low byte) t bvdv t oldv t xlol t ohdz 281 atmega169v/l 2514j?avr?12/03 notes: 1. t wlrh is valid for the write flash, write eeprom, write fuse bits and write lock bits commands. 2. t wlrh_ce is valid for the chip erase command. serial downloading both the flash and eeprom memory arrays can be programmed using the serial spi bus while reset is pulled to gnd. the serial interface consists of pins sck, mosi (input) and miso (output). after reset is set low, the programming enable instruction needs to be executed first before program/erase operations can be executed. note, in table 127 on page 272, the pin mapping for spi programming is listed. not all parts use the spi pins dedicated for the internal spi interface. figure 127. serial programming and verify (1) notes: 1. if the device is clocked by the internal oscillator, it is no need to connect a clock source to the xtal1 pin. 2. v cc - 0.3v < avcc < v cc + 0.3v, however, avcc should always be within 1.8 - 5.5v when programming the eeprom, an auto-erase cycle is built into the self-timed pro- gramming operation (in the serial mode only) and there is no need to first execute the chip erase instruction. the chip erase operation turns the content of every memory location in both the program and eeprom arrays into 0xff. depending on cksel fuses, a valid clock must be present. the minimum low and high periods for the serial clock (sck) input are defined as follows: low:> 2 cpu clock cycles for f ck < 12 mhz, 3 cpu clock cycles for f ck >= 12 mhz high:> 2 cpu clock cycles for f ck < 12 mhz, 3 cpu clock cycles for f ck >= 12 mhz t bvdv bs1 valid to data valid 0 250 ns t oldv oe low to data valid 250 ns t ohdz oe high to data tri-stated 250 ns table 128. parallel programming characteristics, v cc = 5v 10% (continued) symbol parameter min typ max units vcc gnd xtal1 sck miso mosi reset +1.8 - 5.5v avcc +1.8 - 5.5v (2) 282 atmega169v/l 2514j?avr?12/03 serial programming algorithm when writing serial data to the atmega169, data is clocked on the rising edge of sck. when reading data from the atmega169, data is clocked on the falling edge of sck. see figure 128 for timing details. to program and verify the atmega169 in the serial programming mode, the following sequence is recommended (see four byte instruction formats in table 130 ): 1. power-up sequence: apply power between v cc and gnd while reset and sck are set to ?0?. in some systems, the programmer can not guarantee that sck is held low during power-up. in this case, reset must be given a positive pulse of at least two cpu clock cycles duration after sck has been set to ?0?. 2. wait for at least 20 ms and enable serial programming by sending the program- ming enable serial instruction to pin mosi. 3. the serial programming instructions will not work if the communication is out of synchronization. when in sync. the second byte (0x53), will echo back when issuing the third byte of the programming enable instruction. whether the echo is correct or not, all four bytes of the instruction must be transmitted. if the 0x53 did not echo back, give reset a positive pulse and issue a new programming enable command. 4. the flash is programmed one page at a time. the page size is found in table 125 on page 272. the memory page is loaded one byte at a time by supplying the 6 lsb of the address and data together with the load program memory page instruction. to ensure correct loading of the page, the data low byte must be loaded before data high byte is applied for a given address. the program memory page is stored by loading the write program memory page instruction with the 8 msb of the address. if polling is not used, the user must wait at least t wd_flash before issuing the next page. (see table 129.) accessing the serial programming interface before the flash write operation completes can result in incorrect programming. 5. the eeprom array is programmed one byte at a time by supplying the address and data together with the appropriate write instruction. an eeprom memory location is first automatically erased before new data is written. if polling is not used, the user must wait at least t wd_eeprom before issuing the next byte. (see table 129.) in a chip erased device, no 0xffs in the data file(s) need to be programmed. 6. any memory location can be verified by using the read instruction which returns the content at the selected address at serial output miso. 7. at the end of the programming session, reset can be set high to commence normal operation. 8. power-off sequence (if needed): set reset to ?1?. tur n v cc power off. data polling flash when a page is being programmed into the flash, reading an address location within the page being programmed will give the value 0xff. at the time the device is ready for a new page, the programmed value will read correctly. this is used to determine when the next page can be written. note that the entire page is written simultaneously and any address within the page can be used for polling. data polling of the flash will not work for the value 0xff, so when programming this value, the user will have to wait for at least t wd_flash before programming the next page. as a chip-erased device contains 0xff in all locations, programming of addresses that are meant to contain 0xff, can be skipped. see table 129 for t wd_flash value. 283 atmega169v/l 2514j?avr?12/03 data polling eeprom when a new byte has been written and is being programmed into eeprom, reading the address location being programmed will give the value 0xff. at the time the device is ready for a new byte, the programmed value will read correctly. this is used to deter- mine when the next byte can be written. this will not work for the value 0xff, but the user should have the following in mind: as a chip-erased device contains 0xff in all locations, programming of addresses that are meant to contain 0xff, can be skipped. this does not apply if the eeprom is re-programmed without chip erasing the device. in this case, data polling cannot be used for the value 0xff, and the user will have to wait at least t wd_eeprom before programming the next byte. see table 129 for t wd_eeprom value. figure 128. serial programming waveforms table 129. minimum wait delay before writing the next flash or eeprom location symbol minimum wait delay t wd_fuse 4.5 ms t wd_flash 4.5 ms t wd_eeprom 9.0 ms t wd_erase 9.0 ms msb msb lsb lsb serial clock input (sck) serial data input (mosi) (miso) sample serial data output table 130. serial programming instruction set instruction instruction format operation byte 1 byte 2 byte 3 byte4 programming enable 1010 1100 0101 0011 xxxx xxxx xxxx xxxx enable serial programming after reset goes low. chip erase 1010 1100 100x xxxx xxxx xxxx xxxx xxxx chip erase eeprom and flash. read program memory 0010 h 000 000 a aaaa bbbb bbbb oooo oooo read h (high or low) data o from program memory at word address a : b . load program memory page 0100 h 000 000x xxxx xx bb bbbb iiii iiii write h (high or low) data i to program memory page at word address b . data low byte must be loaded before data high byte is applied within the same address. write program memory page 0100 1100 000 a aaaa bb xx xxxx xxxx xxxx write program memory page at address a : b . read eeprom memory 1010 0000 000x xx aa bbbb bbbb oooo oooo read data o from eeprom memory at address a : b . 284 atmega169v/l 2514j?avr?12/03 note: a = address high bits, b = address low bits, h = 0 - low byte, 1 - high byte, o = data out, i = data in, x = don?t care write eeprom memory 1100 0000 000x xx aa bbbb bbbb iiii iiii write data i to eeprom memory at address a : b . load eeprom memory page (page access) 1100 0001 0000 0000 0000 00 bb iiii iiii load data i to eeprom memory page buffer. after data is loaded, program eeprom page. write eeprom memory page (page access) 1100 0010 00xx xx aa bbbb bb 00 xxxx xxxx write eeprom page at address a : b . read lock bits 0101 1000 0000 0000 xxxx xxxx xx oo oooo read lock bits. ?0? = programmed, ?1? = unprogrammed. see table 116 on page 266 for details. write lock bits 1010 1100 111x xxxx xxxx xxxx 11 ii iiii write lock bits. set bits = ?0? to program lock bits. see table 116 on page 266 for details. read signature byte 0011 0000 000x xxxx xxxx xx bb oooo oooo read signature byte o at address b . write fuse bits 1010 1100 1010 0000 xxxx xxxx iiii iiii set bits = ?0? to program, ?1? to unprogram. see table 88 on page 205 for details. write fuse high bits 1010 1100 1010 1000 xxxx xxxx iiii iiii set bits = ?0? to program, ?1? to unprogram. see table 87 on page 197 for details. write extended fuse bits 1010 1100 1010 0100 xxxx xxxx xxxx xxii set bits = ?0? to program, ?1? to unprogram. see table 118 on page 267 for details. read fuse bits 0101 0000 0000 0000 xxxx xxxx oooo oooo read fuse bits. ?0? = programmed, ?1? = unprogrammed. see table 88 on page 205 for details. read fuse high bits 0101 1000 0000 1000 xxxx xxxx oooo oooo read fuse high bits. ?0? = pro- grammed, ?1? = unprogrammed. see table 87 on page 197 for details. read extended fuse bits 0101 0000 0000 1000 xxxx xxxx oooo oooo read extended fuse bits. ?0? = pro- grammed, ?1? = unprogrammed. see table 118 on page 267 for details. read calibration byte 0011 1000 000x xxxx 0000 0000 oooo oooo read calibration byte poll rdy/bsy 1111 0000 0000 0000 xxxx xxxx xxxx xxx o if o = ?1?, a programming operation is still busy. wait until this bit returns to ?0? before applying another command. table 130. serial programming instruction set instruction instruction format operation byte 1 byte 2 byte 3 byte4 285 atmega169v/l 2514j?avr?12/03 spi serial programming characteristics for characteristics of the spi module see ?spi timing characteristics? on page 300. programming via the jtag interface programming through the jtag interface requi res control of the four jtag specific pins: tck, tms, tdi, and tdo. control of the reset and clock pins is not required. to be able to use the jtag interface, the jtagen fuse must be programmed. the device is default shipped with the fuse programmed. in addition, the jtd bit in mcucsr must be cleared. alternatively, if the jtd bit is set, the external reset can be forced low. then, the jtd bit will be cleared after two chip clocks, and the jtag pins are available for programming. this provides a means of using the jtag pins as normal port pins in running mode while still allowing in-system programming via the jtag interface. note that this technique can not be used when using the jtag pins for boundary-scan or on- chip debug. in these cases the jtag pins must be dedicated for this purpose. during programming the clock frequency of the tck input must be less than the maxi- mum frequency of the chip. the system clock prescaler can not be used to divide the tck clock input into a sufficiently low frequency. as a definition in this datasheet, the lsb is shifted in and out first of all shift registers. programming specific jtag instructions the instruction register is 4-bit wide, supporting up to 16 instructions. the jtag instructions useful for programming are listed below. the opcode for each instruction is shown behind the instruction name in hex format. the text describes which data register is selected as path between tdi and tdo for each instruction. the run-test/idle state of the tap controller is used to generate internal clocks. it can also be used as an idle state between jtag sequences. the state machine sequence for changing the instruction word is shown in figure 129. 286 atmega169v/l 2514j?avr?12/03 figure 129. state machine sequence for changing the instruction word avr_reset (0xc) the avr specific public jtag instruction for setting the avr device in the reset mode or taking the device out from the reset mode. the tap controller is not reset by this instruction. the one bit reset register is selected as data register. note that the reset will be active as long as there is a logic ?one? in the reset chain. the output from this chain is not latched. the active states are: shift-dr: the reset register is shifted by the tck input. prog_enable (0x4) the avr specific public jtag instruction for enabling programming via the jtag port. the 16-bit programming enable register is selected as data register. the active states are the following: shift-dr: the programming enable signature is shifted into the data register. update-dr: the programming enable signature is compared to the correct value, and programming mode is entered if the signature is valid. test-logic-reset run-test/idle shift-dr exit1-dr pause-dr exit2-dr update-dr select-ir scan capture-ir shift-ir exit1-ir pause-ir exit2-ir update-ir select-dr scan capture-dr 0 1 0 11 1 00 00 11 1 0 1 1 0 1 0 0 1 0 1 1 0 1 0 0 0 0 1 1 287 atmega169v/l 2514j?avr?12/03 prog_commands (0x5) the avr specific public jtag instruction for entering programming commands via the jtag port. the 15-bit programming command register is selected as data register. the active states are the following: capture-dr: the result of the previous command is loaded into the data register. shift-dr: the data register is shifted by the tck input, shifting out the result of the previous command and shifting in the new command. update-dr: the programming command is applied to the flash inputs run-test/idle: one clock cycle is generated, executing the applied command (not always required, see table 131 below). prog_pageload (0x6) the avr specific public jtag instruction to directly load the flash data page via the jtag port. an 8-bit flash data byte register is selected as the data register. this is physically the 8 lsbs of the programming command register. the active states are the following: shift-dr: the flash data byte register is shifted by the tck input. update-dr: the content of the flash data byte register is copied into a temporary register. a write sequence is initiated that within 11 tck cycles loads the content of the temporary register into the flash page buffer. the avr automatically alternates between writing the low and the high byte for each new update-dr state, starting with the low byte for the first update-dr encountered after entering the prog_pageload command. the program counter is pre-incremented before writing the low byte, except for the first written byte. this ensures that the first data is written to the address set up by prog_commands, and loading the last location in the page buffer does not make the program counter increment into the next page. prog_pageread (0x7) the avr specific public jtag instruction to directly capture the flash content via the jtag port. an 8-bit flash data byte register is selected as the data register. this is physically the 8 lsbs of the programming command register. the active states are the following: capture-dr: the content of the selected flash byte is captured into the flash data byte register. the avr automatically alternates between reading the low and the high byte for each new capture-dr state, starting with the low byte for the first capture-dr encountered after entering the prog_pageread command. the program counter is post-incremented after reading each high byte, including the first read byte. this ensures that the first data is captured from the first address set up by prog_commands, and reading the last location in the page makes the program counter increment into the next page. shift-dr: the flash data byte register is shifted by the tck input. data registers the data registers are selected by the jtag instruction registers described in section ?programming specific jtag instructions? on page 285. the data registers relevant for programming operations are: reset register programming enable register programming command register flash data byte register 288 atmega169v/l 2514j?avr?12/03 reset register the reset register is a test data register used to reset the part during programming. it is required to reset the part before entering programming mode. a high value in the reset register corresponds to pulling the external reset low. the part is reset as long as there is a high value present in the reset register. depending on the fuse settings for the clock options, the part will remain reset for a reset time-out period (refer to ?clock sources? on page 24) after releasing the reset register. the out- put from this data register is not latched, so the reset will take place immediately, as shown in figure 107 on page 234. programming enable register the programming enable register is a 16-bit register. the contents of this register is compared to the programming enable signature, binary code 0b1010_0011_0111_0000. when the contents of the register is equal to the program- ming enable signature, programming via the jtag port is enabled. the register is reset to 0 on power-on reset, and should always be reset when leaving programming mode. figure 130. programming enable register tdi tdo d a t a = dq clockdr & prog_enable programming enable 0xa370 289 atmega169v/l 2514j?avr?12/03 programming command register the programming command register is a 15-bit register. this register is used to seri- ally shift in programming commands, and to serially shift out the result of the previous command, if any. the jtag programming instruction set is shown in table 131. the state sequence when shifting in the programming commands is illustrated in figure 132. figure 131. programming command register tdi tdo s t r o b e s a d d r e s s / d a t a flash eeprom fuses lock bits 290 atmega169v/l 2514j?avr?12/03 table 131. jtag programming instruction set a = address high bits, b = address low bits, h = 0 - low byte, 1 - high byte, o = data out, i = data in, x = don?t care instruction tdi sequence tdo sequence notes 1a. chip erase 0100011_10000000 0110001_10000000 0110011_10000000 0110011_10000000 xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx 1b. poll for chip erase complete 0110011_10000000 xxxxx o x_xxxxxxxx (2) 2a. enter flash write 0100011_00010000 xxxxxxx_xxxxxxxx 2b. load address high byte 0000111_ aaaaaaaa xxxxxxx_xxxxxxxx (9) 2c. load address low byte 0000011_ bbbbbbbb xxxxxxx_xxxxxxxx 2d. load data low byte 0010011_ iiiiiiii xxxxxxx_xxxxxxxx 2e. load data high byte 0010111_ iiiiiiii xxxxxxx_xxxxxxxx 2f. latch data 0110111_00000000 1110111_00000000 0110111_00000000 xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx (1) 2g. write flash page 0110111_00000000 0110101_00000000 0110111_00000000 0110111_00000000 xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx (1) 2h. poll for page write complete 0110111_00000000 xxxxx o x_xxxxxxxx (2) 3a. enter flash read 0100011_00000010 xxxxxxx_xxxxxxxx 3b. load address high byte 0000111_ aaaaaaaa xxxxxxx_xxxxxxxx (9) 3c. load address low byte 0000011_ bbbbbbbb xxxxxxx_xxxxxxxx 3d. read data low and high byte 0110010_00000000 0110110_00000000 0110111_00000000 xxxxxxx_xxxxxxxx xxxxxxx_ oooooooo xxxxxxx_ oooooooo low byte high byte 4a. enter eeprom write 0100011_00010001 xxxxxxx_xxxxxxxx 4b. load address high byte 0000111_ aaaaaaaa xxxxxxx_xxxxxxxx (9) 4c. load address low byte 0000011_ bbbbbbbb xxxxxxx_xxxxxxxx 4d. load data byte 0010011_ iiiiiiii xxxxxxx_xxxxxxxx 4e. latch data 0110111_00000000 1110111_00000000 0110111_00000000 xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx (1) 4f. write eeprom page 0110011_00000000 0110001_00000000 0110011_00000000 0110011_00000000 xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx (1) 4g. poll for page write complete 0110011_00000000 xxxxx o x_xxxxxxxx (2) 5a. enter eeprom r ead 0100011_00000011 xxxxxxx_xxxxxxxx 5b. load address high byte 0000111_ aaaaaaaa xxxxxxx_xxxxxxxx (9) 5c. load address low byte 0000011_ bbbbbbbb xxxxxxx_xxxxxxxx 291 atmega169v/l 2514j?avr?12/03 5d. read data byte 0110011_ bbbbbbbb 0110010_00000000 0110011_00000000 xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_ oooooooo 6a. enter fuse write 0100011_01000000 xxxxxxx_xxxxxxxx 6b. load data low byte (6) 0010011_ iiiiiiii xxxxxxx_xxxxxxxx (3) 6c. write fuse extended byte 0111011_00000000 0111001_00000000 0111011_00000000 0111011_00000000 xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx (1) 6d. poll for fuse write complete 0110111_00000000 xxxxx o x_xxxxxxxx (2) 6e. load data low byte (7) 0010011_ iiiiiiii xxxxxxx_xxxxxxxx (3) 6f. write fuse high byte 0110111_00000000 0110101_00000000 0110111_00000000 0110111_00000000 xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx (1) 6g. poll for fuse write complete 0110111_00000000 xxxxx o x_xxxxxxxx (2) 6h. load data low byte (7) 0010011_ iiiiiiii xxxxxxx_xxxxxxxx (3) 6i. write fuse low byte 0110011_00000000 0110001_00000000 0110011_00000000 0110011_00000000 xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx (1) 6j. poll for fuse write complete 0110011_00000000 xxxxx o x_xxxxxxxx (2) 7a. enter lock bit write 0100011_00100000 xxxxxxx_xxxxxxxx 7b. load data byte (9) 0010011_11 iiiiii xxxxxxx_xxxxxxxx (4) 7c. write lock bits 0110011_00000000 0110001_00000000 0110011_00000000 0110011_00000000 xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx (1) 7d. poll for lock bit write complete 0110011_00000000 xxxxx o x_xxxxxxxx (2) 8a. enter fuse/lock bit read 0100011_00000100 xxxxxxx_xxxxxxxx 8b. read extended fuse byte (6) 0111010_00000000 0111011_00000000 xxxxxxx_xxxxxxxx xxxxxxx_ oooooooo 8c. read fuse high byte (7) 0111110_00000000 0111111_00000000 xxxxxxx_xxxxxxxx xxxxxxx_ oooooooo 8d. read fuse low byte (8) 0110010_00000000 0110011_00000000 xxxxxxx_xxxxxxxx xxxxxxx_ oooooooo 8e. read lock bits (9) 0110110_00000000 0110111_00000000 xxxxxxx_xxxxxxxx xxxxxxx_xx oooooo (5) table 131. jtag programming instruction (continued) set (continued) a = address high bits, b = address low bits, h = 0 - low byte, 1 - high byte, o = data out, i = data in, x = don?t care instruction tdi sequence tdo sequence notes 292 atmega169v/l 2514j?avr?12/03 notes: 1. this command sequence is not required if the seven msb are correctly set by the previous command sequence (which is normally the case). 2. repeat until o = ?1?. 3. set bits to ?0? to program the corresponding fuse, ?1? to unprogram the fuse. 4. set bits to ?0? to program the corresponding lock bit, ?1? to leave the lock bit unchanged. 5. ?0? = programmed, ?1? = unprogrammed. 6. the bit mapping for fuses extended byte is listed in table 118 on page 267 7. the bit mapping for fuses high byte is listed in table 119 on page 268 8. the bit mapping for fuses low byte is listed in table 120 on page 268 9. the bit mapping for lock bits byte is listed in table 116 on page 266 10. address bits exceeding pcmsb and eeamsb (table 125 and table 126) are don?t care 11. all tdi and tdo sequences are represented by binary digits (0b...). 8f. read fuses and lock bits 0111010_00000000 0111110_00000000 0110010_00000000 0110110_00000000 0110111_00000000 xxxxxxx_xxxxxxxx xxxxxxx_ oooooooo xxxxxxx_ oooooooo xxxxxxx_ oooooooo xxxxxxx_ oooooooo (5) fuse ext. byte fuse high byte fuse low byte lock bits 9a. enter signature by te read 0100011_00001000 xxxxxxx_xxxxxxxx 9b. load address byte 0000011_ bbbbbbbb xxxxxxx_xxxxxxxx 9c. read signature byte 0110010_00000000 0110011_00000000 xxxxxxx_xxxxxxxx xxxxxxx_ oooooooo 10a. enter calibration byte read 0100011_00001000 xxxxxxx_xxxxxxxx 10b. load address byte 0000011_ bbbbbbbb xxxxxxx_xxxxxxxx 10c. read calibration byte 0110110_00000000 0110111_00000000 xxxxxxx_xxxxxxxx xxxxxxx_ oooooooo 11a. load no operation command 0100011_00000000 0110011_00000000 xxxxxxx_xxxxxxxx xxxxxxx_xxxxxxxx table 131. jtag programming instruction (continued) set (continued) a = address high bits, b = address low bits, h = 0 - low byte, 1 - high byte, o = data out, i = data in, x = don?t care instruction tdi sequence tdo sequence notes 293 atmega169v/l 2514j?avr?12/03 figure 132. state machine sequence for changing/reading the data word flash data byte register the flash data byte register provides an efficient way to load the entire flash page buffer before executing page write, or to read out/verify the content of the flash. a state machine sets up the control signals to the flash and senses the strobe signals from the flash, thus only the data words need to be shifted in/out. the flash data byte register actually consists of the 8-bit scan chain and a 8-bit tempo- rary register. during page load, the update-dr state copies the content of the scan chain over to the temporary register and initiates a write sequence that within 11 tck cycles loads the content of the temporary re gister into the flash page buffer. the avr automatically alternates between writing the low and the high byte for each new update- dr state, starting with the low byte for the first update-dr encountered after entering the prog_pageload command. the progra m counter is pre- incremented before writing the low byte, except for the first written byte. this ensures that the first data is written to the address set up by prog_commands, and loading the last location in the page buffer does not make the program counter increment into the next page. during page read, the content of the selected flash byte is captured into the flash data byte register during the capture-dr state. the avr automatically alternates between reading the low and the high byte for each new capture-dr state, starting with the low byte for the first capture-dr encountered after entering the prog_pageread command. the program counter is post-incremented after reading each high byte, test-logic-reset run-test/idle shift-dr exit1-dr pause-dr exit2-dr update-dr select-ir scan capture-ir shift-ir exit1-ir pause-ir exit2-ir update-ir select-dr scan capture-dr 0 1 0 11 1 00 00 11 1 0 1 1 0 1 0 0 1 0 1 1 0 1 0 0 0 0 1 1 294 atmega169v/l 2514j?avr?12/03 including the first read byte. this ensures that the first data is captured from the first address set up by prog_commands, and reading the last location in the page makes the program counter increment into the next page. figure 133. flash data byte register the state machine controlling the flash data byte register is clocked by tck. during normal operation in which eight bits are shifted for each flash byte, the clock cycles needed to navigate through the tap controller automatically feeds the state machine for the flash data byte register with sufficient number of clock pulses to complete its oper- ation transparently for the user. however, if too few bits are shifted between each update-dr state during page load, the tap controller should stay in the run-test/idle state for some tck cycles to ensure that there are at least 11 tck cycles between each update-dr state. programming algorithm all references below of type ?1a?, ?1b?, and so on, refer to table 131. entering programming mode 1. enter jtag instruction avr_reset and shift 1 in the reset register. 2. enter instruction prog_enable and shift 0b1010_0011_0111_0000 in the programming enable register. leaving programming mode 1. enter jtag instruction prog_commands. 2. disable all programming instructions by using no operation instruction 11a. 3. enter instruction prog_enable and shift 0b0000_0000_0000_0000 in the programming enable register. 4. enter jtag instruction avr_reset and shift 0 in the reset register. performing chip erase 1. enter jtag instruction prog_commands. 2. start chip erase using programming instruction 1a. 3. poll for chip erase complete using programming instruction 1b, or wait for t wlrh_ce (refer to table 128 on page 280). tdi tdo d a t a flash eeprom fuses lock bits strobes address state machine 295 atmega169v/l 2514j?avr?12/03 programming the flash before programming the flash a chip erase must be performed, see ?performing chip erase? on page 294. 1. enter jtag instruction prog_commands. 2. enable flash write using programming instruction 2a. 3. load address high byte using programming instruction 2b. 4. load address low byte using programming instruction 2c. 5. load data using programming instructions 2d, 2e and 2f. 6. repeat steps 4 and 5 for all instruction words in the page. 7. write the page using programming instruction 2g. 8. poll for flash write complete using programming instruction 2h, or wait for t wlrh (refer to table 128 on page 280). 9. repeat steps 3 to 7 until all data have been programmed. a more efficient data transfer can be achieved using the prog_pageload instruction: 1. enter jtag instruction prog_commands. 2. enable flash write using programming instruction 2a. 3. load the page address using programming instructions 2b and 2c. pcword (refer to table 125 on page 272) is used to address within one page and must be written as 0. 4. enter jtag instruction prog_pageload. 5. load the entire page by shifting in all instruction words in the page byte-by-byte, starting with the lsb of the first instruction in the page and ending with the msb of the last instruction in the page. use update-dr to copy the contents of the flash data byte register into the flash page location and to auto-increment the program counter before each new word. 6. enter jtag instruction prog_commands. 7. write the page using programming instruction 2g. 8. poll for flash write complete using programming instruction 2h, or wait for t wlrh (refer to table 128 on page 280). 9. repeat steps 3 to 8 until all data have been programmed. reading the flash 1. enter jtag instruction prog_commands. 2. enable flash read using programming instruction 3a. 3. load address using programming instructions 3b and 3c. 4. read data using programming instruction 3d. 5. repeat steps 3 and 4 until all data have been read. a more efficient data transfer can be achieved using the prog_pageread instruction: 1. enter jtag instruction prog_commands. 2. enable flash read using programming instruction 3a. 3. load the page address using programming instructions 3b and 3c. pcword (refer to table 125 on page 272) is used to address within one page and must be written as 0. 4. enter jtag instruction prog_pageread. 5. read the entire page (or flash) by shifting out all instruction words in the page (or flash), starting with the lsb of the first instruction in the page (flash) and 296 atmega169v/l 2514j?avr?12/03 ending with the msb of the last instruction in the page (flash). the capture-dr state both captures the data from the flash, and also auto-increments the pro- gram counter after each word is read. note that capture-dr comes before the shift-dr state. hence, the first byte which is shifted out contains valid data. 6. enter jtag instruction prog_commands. 7. repeat steps 3 to 6 until all data have been read. programming the eeprom before programming the eeprom a chip erase must be performed, see ?performing chip erase? on page 294. 1. enter jtag instruction prog_commands. 2. enable eeprom write using programming instruction 4a. 3. load address high byte using programming instruction 4b. 4. load address low byte using programming instruction 4c. 5. load data using programming instructions 4d and 4e. 6. repeat steps 4 and 5 for all data bytes in the page. 7. write the data using programming instruction 4f. 8. poll for eeprom write complete using programming instruction 4g, or wait for t wlrh (refer to table 128 on page 280). 9. repeat steps 3 to 8 until all data have been programmed. note that the prog_pageload instruction can not be used when programming the eeprom. reading the eeprom 1. enter jtag instruction prog_commands. 2. enable eeprom read using programming instruction 5a. 3. load address using programming instructions 5b and 5c. 4. read data using programming instruction 5d. 5. repeat steps 3 and 4 until all data have been read. note that the prog_pageread instruction can not be used when reading the eeprom. programming the fuses 1. enter jtag instruction prog_commands. 2. enable fuse write using programming instruction 6a. 3. load data high byte using programming instructions 6b. a bit value of ?0? will pro- gram the corresponding fuse, a ?1? will unprogram the fuse. 4. write fuse high byte using programming instruction 6c. 5. poll for fuse write complete using programming instruction 6d, or wait for t wlrh (refer to table 128 on page 280). 6. load data low byte using programming instructions 6e. a ?0? will program the fuse, a ?1? will unprogram the fuse. 7. write fuse low byte using programming instruction 6f. 8. poll for fuse write complete using programming instruction 6g, or wait for t wlrh (refer to table 128 on page 280). 297 atmega169v/l 2514j?avr?12/03 programming the lock bits 1. enter jtag instruction prog_commands. 2. enable lock bit write using programming instruction 7a. 3. load data using programming instructions 7b. a bit value of ?0? will program the corresponding lock bit, a ?1? will leave the lock bit unchanged. 4. write lock bits using programming instruction 7c. 5. poll for lock bit write complete using programming instruction 7d, or wait for t wlrh (refer to table 128 on page 280). reading the fuses and lock bits 1. enter jtag instruction prog_commands. 2. enable fuse/lock bit read using programming instruction 8a. 3. to read all fuses and lock bits, use programming instruction 8e. to only read fuse high byte, use programming instruction 8b. to only read fuse low byte, use programming instruction 8c. to only read lock bits, use programming instruction 8d. reading the signature bytes 1. enter jtag instruction prog_commands. 2. enable signature byte read using programming instruction 9a. 3. load address 0x00 using programming instruction 9b. 4. read first signature byte using programming instruction 9c. 5. repeat steps 3 and 4 with address 0x01 and address 0x02 to read the second and third signature bytes, respectively. reading the calibration byte 1. enter jtag instruction prog_commands. 2. enable calibration byte read using programming instruction 10a. 3. load address 0x00 using programming instruction 10b. 4. read the calibration byte using programming instruction 10c. 298 atmega169v/l 2514j?avr?12/03 electrical characteristics absolute maximum ratings* dc characteristics operating temperature .................................. -55 c to +125 c *notice: stresses beyond those listed under ?absolute maximum ratings? may cause permanent dam- age to the device. this is a stress rating only and functional operation of the device at these or other conditions beyond those indicated in the operational sections of this specification is not implied. exposure to absolute maximum rating conditions for extended periods may affect device reliability. storage temperature ..................................... -65c to +150c voltage on any pin except reset with respect to ground ................................-0.5v to v cc +0.5v voltage on reset with respect to ground......-0.5v to +13.0v maximum operating voltage ............................................ 6.0v dc current per i/o pin ............................................... 40.0 ma dc current v cc and gnd pins................................ 200.0 ma t a = -40 c to 85 c, v cc = 1.8v to 5.5v (unless otherwise noted) symbol parameter condition min. typ. max. units v il input low voltage, except xtal1 pin v cc = 1.8v - 2.4v v cc = 2.4v - 5.5v -0.5 -0.5 0.2v cc (1) 0.3v cc (1) v v il1 input low voltage, xtal1 pin v cc = 1.8v - 5.5v -0.5 0.1v cc (1) v v ih input high voltage, except xtal1 and reset pins v cc = 1.8v - 2.4v v cc = 2.4v - 5.5v 0.7v cc (2) 0.6v cc (2) v cc + 0.5 v cc + 0.5 v v ih1 input high voltage, xtal1 pin v cc = 1.8v - 2.4v v cc = 2.4v - 5.5v 0.8v cc (2) 0.7v cc (2) v cc + 0.5 v cc + 0.5 v v ih2 input high voltage, reset pin v cc = 1.8v - 5.5v 0.9v cc (2) v cc + 0.5 v v ol output low voltage (3) , port a, c, d, e, f, g i ol = 10ma, v cc = 5v i ol = 5ma, v cc = 3v 0.7 0.5 v v ol1 output low voltage (3) , port b i ol = 20ma, v cc = 5v i ol = 10ma, v cc = 3v 0.7 0.5 v v oh output high voltage (4) , port a, c, d, e, f, g i oh = -10ma, v cc = 5v i oh = -5ma, v cc = 3v 4.2 2.3 v v oh1 output high voltage (4) , port b i oh = -20ma, v cc = 5v i oh = -10ma, v cc = 3v 4.2 2.3 v i il input leakage current i/o pin v cc = 5.5v, pin low (absolute value) 1a i ih input leakage current i/o pin v cc = 5.5v, pin high (absolute value) 1a r rst reset pull-up resistor 30 60 k ? r pu i/o pin pull-up resistor 20 50 k ? 299 atmega169v/l 2514j?avr?12/03 note: 1. ?max? means the highest value where the pin is guaranteed to be read as low 2. ?min? means the lowest value where the pin is guaranteed to be read as high 3. although each i/o port can sink more than the test conditions (20 ma at v cc = 5v, 10 ma at v cc = 3v for port b and 10 ma at v cc = 5v, 5 ma at v cc = 3v for all other ports) under steady state conditions (non-transient), the following must be observed: tqfp and mlf package: 1] the sum of all iol, for all ports, should not exceed 400 ma. 2] the sum of all iol, for ports a0 - a7, c4 - c7, g2 should not exceed 100 ma. 3] the sum of all iol, for ports b0 - b7, e0 - e7, g3 - g5 should not exceed 100 ma. 4] the sum of all iol, for ports d0 - d7, c0 - c3, g0 - g1 should not exceed 100 ma. 5] the sum of all iol, for ports f0 - f7, should not exceed 100 ma. if iol exceeds the test condition, vol may exceed the related specification. pins are not guaranteed to sink current greater than the listed test condition. 4. although each i/o port can source more than the test conditions (20 ma at v cc = 5v, 10 ma at v cc = 3v for port b and 10ma at v cc = 5v, 5 ma at v cc = 3v for all other ports) under steady state conditions (non-transient), the following must be observed: tqfp and mlf package: 1] the sum of all iol, for all ports, should not exceed 400 ma. 2] the sum of all iol, for ports a0 - a7, c4 - c7, g2 should not exceed 100 ma. 3] the sum of all iol, for ports b0 - b7, e0 - e7, g3 - g5 should not exceed 100 ma. 4] the sum of all iol, for ports d0 - d7, c0 - c3, g0 - g1 should not exceed 100 ma. 5] the sum of all iol, for ports f0 - f7, should not exceed 100 ma. if ioh exceeds the test condition, voh may exceed the related specification. pins are not guaranteed to source current greater than the listed test condition. i cc power supply current active 1mhz, v cc = 2v (atmega169v) 0.55 ma active 4mhz, v cc = 3v (atmega169l) 3.5 ma active 8mhz, v cc = 5v (atmega169) 12 ma idle 1mhz, v cc = 2v (atmega169v) 0.25 0.5 ma idle 4mhz, v cc = 3v (atmega169l) 1.5 ma idle 8mhz, v cc = 5v (atmega169) 5.5 ma power-down mode wdt enabled, v cc = 3v <8 10 a wdt disabled, v cc = 3v <1 2 a v acio analog comparator input offset voltage v cc = 5v v in = v cc /2 <10 40 mv i aclk analog comparator input leakage current v cc = 5v v in = v cc /2 -50 50 na t acid analog comparator propagation delay v cc = 2.7v v cc = 4.0v 750 500 ns t a = -40 c to 85 c, v cc = 1.8v to 5.5v (unless otherwise noted) (continued) symbol parameter condition min. typ. max. units 300 atmega169v/l 2514j?avr?12/03 external clock drive waveforms figure 134. external clock drive waveforms external clock drive spi timing characteristics see figure 135 and figure 136 for details. v il1 v ih1 table 132. external clock drive symbol parameter v cc =1.8-5.5v v cc =2.7-5.5v v cc =4.5-5.5v units min. max. min. max. min. max. 1/t clcl oscillator frequency 0108016mhz t clcl clock period 1000 125 62.5 ns t chcx high time 400 50 25 ns t clcx low time 400 50 25 ns t clch rise time 2.0 1.6 0.5 s t chcl fall time 2.0 1.6 0.5 s ? t clcl change in period from one clock cycle to the next 22 2% table 133. spi timing parameters description mode min typ max 1 sck period master see table 69 ns 2 sck high/low master 50% duty cycle 3 rise/fall time master 3.6 4 setup master 10 5holdmaster 10 6 out to sck master 0.5 t sck 7 sck to out master 10 8 sck to out high master 10 9ss low to out slave 15 10 sck period slave 4 t ck 11 sck high/low (1) slave 2 t ck 12 rise/fall time slave 1.6 s 301 atmega169v/l 2514j?avr?12/03 note: 1. in spi programming mode the minimum sck high/low period is: - 2 t clcl for f ck < 12 mhz - 3 t clcl for f ck > 12 mhz figure 135. spi interface timing requirements (master mode) figure 136. spi interface timing requirements (slave mode) 13 setup slave 10 ns 14 hold slave t ck 15 sck to out slave 15 16 sck to ss high slave 20 17 ss high to tri-state slave 10 18 ss low to sck slave 20 t ck table 133. spi timing parameters description mode min typ max mo si (data output) sck (cpol = 1) mi so (data input) sck (cpol = 0) ss msb lsb lsb msb ... ... 61 22 3 45 8 7 mi so (data output) sck (cpol = 1) mo si (data input) sck (cpol = 0) ss msb lsb lsb msb ... ... 10 11 11 12 13 14 17 15 9 x 16 302 atmega169v/l 2514j?avr?12/03 adc characteristics ? preliminary data note: 1. v diff must be below v ref table 134. adc characteristics symbol parameter condition min typ max units resolution single ended conversion 10 bits differential conversion 8 bits absolute accuracy (including inl, dnl, quantization error, gain and offset error) single ended conversion v ref = 4v, v cc = 4v, adc clock = 200 khz 22.5lsb single ended conversion v ref = 4v, v cc = 4v, adc clock = 1 mhz 4.5 lsb single ended conversion v ref = 4v, v cc = 4v, adc clock = 200 khz noise reduction mode 2lsb single ended conversion v ref = 4v, v cc = 4v, adc clock = 1 mhz noise reduction mode 4.5 lsb integral non-linearity (inl) single ended conversion v ref = 4v, v cc = 4v, adc clock = 200 khz 0.5 lsb differential non-linearity (dnl) single ended conversion v ref = 4v, v cc = 4v, adc clock = 200 khz 0.25 lsb gain error single ended conversion v ref = 4v, v cc = 4v, adc clock = 200 khz 2lsb offset error single ended conversion v ref = 4v, v cc = 4v, adc clock = 200 khz 2lsb conversion time free running conversion 13 260 s clock frequency single ended conversion 50 1000 khz avcc analog supply voltage v cc - 0.3 v cc + 0.3 v v ref reference voltage single ended conversion 1.0 avcc v differential conversion 1.0 avcc - 0.5 v v in input voltage single ended channels gnd v ref v differential conversion 0 avcc (1) v input bandwidth single ended channels 38,5 khz differential channels 4 khz v int internal voltage reference 1.0 1.1 1.2 v r ref reference input resistance 32 k ? r ain analog input resistance 100 m ? 303 atmega169v/l 2514j?avr?12/03 lcd controller characteristics ? preliminary data table 135. lcd controller characteristics symbol parameter condition min typ max units i lcd lcd driver current total for all com and seg pins 100 a r lcd lcd driver output resistance per com or seg pin 10 k ? 304 atmega169v/l 2514j?avr?12/03 atmega169 typical characteristics ? preliminary data the following charts show typical behavior. these figures are not tested during manu- facturing. all current consumption measurements are performed with all i/o pins configured as inputs and with internal pull-ups enabled. a sine wave generator with rail- to-rail output is used as clock source. the power consumption in power-down mode is independent of clock selection. the current consumption is a function of several factors such as: operating voltage, operating frequency, loading of i/o pins, switching rate of i/o pins, code executed and ambient temperature. the dominating factors are operating voltage and frequency. the current drawn from capacitive loaded pins may be estimated (for one pin) as c l * v cc *f where c l = load capacitance, v cc = operating voltage and f = average switch- ing frequency of i/o pin. the parts are characterized at frequencies higher than test limits. parts are not guaran- teed to function properly at frequencies higher than the ordering code indicates. the difference between current consumption in power-down mode with watchdog timer enabled and power-down mode with watchdog timer disabled represents the dif- ferential current drawn by the watchdog timer. active supply current figure 137. active supply current vs. frequency (0.1 - 1.0 mhz) active supply current vs. frequency 0.1 - 1.0 mhz 0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 frequency (mhz) i cc (ma) 5.5v 4.5v 4.0v 3.3v 2.7v 1.8v 5.0v 305 atmega169v/l 2514j?avr?12/03 figure 138. active supply current vs. frequency (1 - 20 mhz) figure 139. active supply current vs. v cc (internal rc oscillator, 8 mhz active supply current vs. frequency 1 - 20 mhz 0 5 10 15 20 25 30 02468101214161820 frequency (mhz) i cc (ma) 5.5v 4.5v 4.0v 3.3v 2.7v 1.8v 5.0v active supply current vs. v cc internal rc oscillator, 8 mhz 0 2 4 6 8 10 12 14 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ma) 85 c 25 c -40 c 306 atmega169v/l 2514j?avr?12/03 figure 140. active supply current vs. v cc (internal rc oscillator, ckdiv8 programmed, 1 mhz) figure 141. active supply current vs. v cc (32 khz external oscillator) active supply current vs. v cc internal rc oscillator, ckdiv8 programmed, 1 mhz 0 0.5 1 1.5 2 2.5 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ma) 85 c 25 c -40 c active supply current vs. v cc 32khz external oscillator 0 10 20 30 40 50 60 70 80 90 100 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) 85 c 25 c 307 atmega169v/l 2514j?avr?12/03 idle supply current figure 142. idle supply current vs. frequency (0.1 - 1.0 mhz) figure 143. idle supply current vs. frequency (1 - 20 mhz) idle supply current vs. frequency 0.1 - 1.0 mhz 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 frequency (mhz) i cc (ma) 5.5v 4.5 v 4.0 v 3.3 v 2.7 v 1.8 v 5.0 v idle supply current vs. frequency 1 - 20 mhz 0 2 4 6 8 10 12 14 16 0 2 4 6 8 10 12 14 16 18 20 frequency (mhz) i cc (ma) 5.5v 4.5v 4.0v 3.3v 2.7v 1.8v 5.0v 308 atmega169v/l 2514j?avr?12/03 figure 144. idle supply current vs. v cc (internal rc oscillator, 8 mhz) figure 145. idle supply current vs. v cc (internal rc oscillator, ckdiv8 programmed, 1mhz) idle supply current vs. v cc internal rc oscillator, 8 mhz 0 1 2 3 4 5 6 7 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ma) 85 c 25 c -40 c idle supply current vs. v cc internal rc oscillator, ckdiv8 programmed, 1 mhz 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ma) 85 c 25 c -40 c 309 atmega169v/l 2514j?avr?12/03 figure 146. idle supply current vs. v cc (32 khz external oscillator) power-down supply current figure 147. power-down supply current vs. v cc (watchdog timer disabled) idle supply current vs. v cc 32khz external oscillator 0 5 10 15 20 25 30 35 40 45 50 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) 85 c 25 c power-down supply current vs. v cc watchdog timer disabled 0 0.5 1 1.5 2 2.5 3 3.5 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) 85 c 25 c -40 c 310 atmega169v/l 2514j?avr?12/03 figure 148. power-down supply current vs. v cc (watchdog timer enabled) power-save supply current figure 149. power-save supply current vs. v cc (watchdog timer disabled) power-down supply current vs. v cc watchdog timer enabled 0 2 4 6 8 10 12 14 16 18 20 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) 85 c 25 c -40 c power-save supply current vs. v cc watchdog timer disabled 0 5 10 15 20 25 30 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) 85 c 25 c 311 atmega169v/l 2514j?avr?12/03 standby supply current figure 150. standby supply current vs. v cc (455 khz resonator, watchdog timer disabled) figure 151. standby supply current vs. v cc (1 mhz resonator, watchdog timer disabled) standby supply current vs. v cc 455 khz resonator, watchdog timer disabled 0 10 20 30 40 50 60 70 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) standby supply current vs. v cc 1 mhz resonator, watchdog timer disabled 0 10 20 30 40 50 60 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) 312 atmega169v/l 2514j?avr?12/03 figure 152. standby supply current vs. v cc (2 mhz resonator, watchdog timer disabled) figure 153. standby supply current vs. v cc (2 mhz xtal, watchdog timer disabled) standby supply current vs. v cc 2 mhz resonator, watchdog timer disabled 0 10 20 30 40 50 60 70 80 90 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) standby supply current vs. v cc 2 mhz xtal, watchdog timer disabled 0 10 20 30 40 50 60 70 80 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) 313 atmega169v/l 2514j?avr?12/03 figure 154. standby supply current vs. v cc (4 mhz resonator, watchdog timer disabled) figure 155. standby supply current vs. v cc (4 mhz xtal, watchdog timer disabled) standby supply current vs. v cc 4 mhz resonator, watchdog timer disabled 0 20 40 60 80 100 120 140 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) standby supply current vs. v cc 4 mhz xtal, watchdog timer disabled 0 20 40 60 80 100 120 140 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) 314 atmega169v/l 2514j?avr?12/03 figure 156. standby supply current vs. v cc (6 mhz resonator, watchdog timer disabled) figure 157. standby supply current vs. v cc (6 mhz xtal, watchdog timer disabled) standby supply current vs. v cc 6 mhz resonator, watchdog timer disabled 0 20 40 60 80 100 120 140 160 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) standby supply current vs. v cc 6 mhz xtal, watchdog timer disabled 0 20 40 60 80 100 120 140 160 180 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) 315 atmega169v/l 2514j?avr?12/03 pin pull-up figure 158. i/o pin pull-up resistor current vs. input voltage (v cc = 5v) figure 159. i/o pin pull-up resistor current vs. input voltage (v cc = 2.7v) i/o pin pull-up resistor current vs. input voltage vcc = 5v 0 20 40 60 80 100 120 140 160 012345 v io (v) i io (ua) 85 c 25 c -40 c i/o pin pull-up resistor current vs. input voltage vcc = 2.7v 0 10 20 30 40 50 60 70 80 90 0 0.5 1 1.5 2 2.5 3 v io (v) i io (ua) 85 c 25 c -40 c 316 atmega169v/l 2514j?avr?12/03 figure 160. i/o pin pull-up resistor current vs. input voltage (v cc = 1.8v) figure 161. reset pull-up resistor current vs. reset pin voltage (v cc = 5v) i/o pin pull-up resistor current vs. input voltage vcc = 1.8v 0 10 20 30 40 50 60 0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2 v op (v) i op (ua) 85 c 25 c -40 c reset pull-up resistor current vs. reset pin voltage vcc = 5v 0 20 40 60 80 100 120 012345 v reset (v) i reset (ua) -40 c 25 c 85 c 317 atmega169v/l 2514j?avr?12/03 figure 162. reset pull-up resistor current vs. reset pin voltage (v cc = 2.7v) figure 163. reset pull-up resistor current vs. reset pin voltage (v cc = 1.8v) reset pull-up resistor current vs. reset pin voltage vcc = 2.7v 0 10 20 30 40 50 60 70 0 0.5 1 1.5 2 2.5 3 v reset (v) i reset (ua) -40 c 25 c 85 c reset pull-up resistor current vs. reset pin voltage vcc = 1.8v 0 5 10 15 20 25 30 35 40 0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2 v reset (v) i reset (ua) -40 c 25 c 85 c 318 atmega169v/l 2514j?avr?12/03 pin driver strength figure 164. i/o pin source current vs. output voltage, ports a, c, d, e, f, g (v cc =5v) figure 165. i/o pin source current vs. output voltage, ports a, c, d, e, f, g (v cc =2.7v) i/o pin source current vs. output voltage, ports a, c, d, e, f, g vcc = 5v 0 10 20 30 40 50 60 70 0123456 v oh (v) i oh (ma) 85 c 25 c -40 c i/o pin source current vs. output voltage, ports a, c, d, e, f, g vcc = 2.7v 0 5 10 15 20 25 0 0.5 1 1.5 2 2.5 3 v oh (v) i oh (ma) 85 c 25 c -40 c 319 atmega169v/l 2514j?avr?12/03 figure 166. i/o pin source current vs. output voltage, ports a, c, d, e, f, g (v cc =1.8v) figure 167. i/o pin source current vs. output voltage, port b (v cc = 5v) i/o pin source current vs. output voltage, ports a, c, d, e, f, g vcc = 1.8v 0 1 2 3 4 5 6 7 8 0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2 v oh (v) i oh (ma) 85 c 25 c -40 c i/o pin source current vs. output voltage, port b vcc = 5v 0 10 20 30 40 50 60 70 80 01234 v oh (v) i oh (ma) 85 c 25 c -40 c 320 atmega169v/l 2514j?avr?12/03 figure 168. i/o pin source current vs. output voltage, port b (v cc = 2.7v) figure 169. i/o pin source current vs. output voltage, port b (v cc = 1.8v) i/o pin source current vs. output voltage, port b vcc = 2.7v 0 5 10 15 20 25 30 35 0 0.5 1 1.5 2 2.5 3 v oh (v) i oh (ma) 85 c 25 c -40 c i/o pin source current vs. output voltage, port b vcc = 1.8v 0 1 2 3 4 5 6 7 8 9 10 0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2 v oh (v) i oh (ma) 85 c 25 c -40 c 321 atmega169v/l 2514j?avr?12/03 figure 170. i/o pin sink current vs. output voltage, ports a, c, d, e, f, g (v cc = 5v) figure 171. i/o pin sink current vs. output voltage, ports a, c, d, e, f, g (v cc = 2.7v) i/o pin sink current vs. output voltage, ports a, c, d, e, f, g vcc = 5v 0 5 10 15 20 25 30 35 40 45 50 0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2 v ol (v) i ol (ma) 85 c 25 c -40 c i/o pin sink current vs. output voltage, ports a, c, d, e, f, g vcc = 2.7v 0 2 4 6 8 10 12 14 16 18 20 0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2 v ol (v) i ol (ma) 85 c 25 c -40 c 322 atmega169v/l 2514j?avr?12/03 figure 172. i/o pin sink current vs. output voltage, ports a, c, d, e, f, g (v cc = 1.8v) figure 173. i/o pin sink current vs. output voltage, port b (v cc = 5v) i/o pin sink current vs. output voltage, ports a, c, d, e, f, g vcc = 1.8v 0 1 2 3 4 5 6 7 0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2 v ol (v) i ol (ma) 85 c 25 c -40 c i/o pin sink current vs. output voltage, port b vcc = 5v 0 10 20 30 40 50 60 70 80 90 0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2 v ol (v) i ol (ma) 85 c 25 c -40 c 323 atmega169v/l 2514j?avr?12/03 figure 174. i/o pin sink current vs. output voltage, port b (v cc = 2.7v) figure 175. i/o pin source current vs. output voltage, port b (v cc = 1.8v) i/o pin sink current vs. output voltage, port b vcc = 2.7v 0 5 10 15 20 25 30 35 0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2 v ol (v) i ol (ma) 85 c 25 c -40 c i/o pin sink current vs. output voltage, port b vcc = 1.8v 0 2 4 6 8 10 12 0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2 v ol (v) i ol (ma) 85 c 25 c -40 c 324 atmega169v/l 2514j?avr?12/03 pin thresholds and hysteresis figure 176. i/o pin input threshold voltage vs. v cc (v ih , i/o pin read as ?1?) figure 177. i/o pin input threshold voltage vs. v cc (v il , i/o pin read as ?0?) i/o pin input threshold voltage vs. v cc vih, i/o pin read as '1' 0 0.5 1 1.5 2 2.5 3 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) threshold (v) 85 c 25 c -40 c i/o pin input threshold voltage vs. v cc vil, i/o pin read as '0' 0 0.5 1 1.5 2 2.5 3 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) threshold (v) 85 c 25 c -40 c 325 atmega169v/l 2514j?avr?12/03 figure 178. i/o pin input hysteresis vs. v cc figure 179. reset input threshold voltage vs. v cc (v ih ,reset pin read as ?1?) i/o pin input hysteresis vs. v cc 0 0.1 0.2 0.3 0.4 0.5 0.6 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) threshold (v) 85 c 25 c -40 c reset input threshold voltage vs. v cc vih, reset pin read as '1' 0 0.5 1 1.5 2 2.5 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) threshold (v) 85 c 25 c -40 c 326 atmega169v/l 2514j?avr?12/03 figure 180. reset input threshold voltage vs. v cc (v il ,reset pin read as ?0?) figure 181. reset input pin hysteresis vs. v cc reset input threshold voltage vs. v cc vil, reset pin read as '0' 0 0.5 1 1.5 2 2.5 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) threshold (v) 85 c 25 c -40 c reset input pin hysteresis vs. v cc 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) threshold (v) 85 c 25 c -40 c 327 atmega169v/l 2514j?avr?12/03 bod thresholds and analog comparator offset figure 182. bod thresholds vs. temperature (bod level is 4.3v) figure 183. bod thresholds vs. temperature (bod level is 2.7v) bod thresholds vs. temperature bodlevel is 4.3v 4 4.1 4.2 4.3 4.4 4.5 4.6 -50 -40 -30 -20 -10 0 10 20 30 40 50 60 70 80 90 100 temperature (?c) threshold (v) rising v cc falling v cc bod thresholds vs. temperature bodlevel is 2.7v 2.4 2.5 2.6 2.7 2.8 2.9 3 -50 -40 -30 -20 -10 0 10 20 30 40 50 60 70 80 90 100 temperature (?c) threshold (v) rising v cc falling v cc 328 atmega169v/l 2514j?avr?12/03 figure 184. bod thresholds vs. temperature (bod level is 1.8v) figure 185. bandgap voltage vs. v cc bod thresholds vs. temperature bodlevel is 1.8v 1.5 1.6 1.7 1.8 1.9 2 2.1 -50 -40 -30 -20 -10 0 10 20 30 40 50 60 70 80 90 100 temperature (?c) threshold (v) rising v cc falling v cc bandgap voltage vs. v cc 1.08 1.09 1.1 1.11 1.12 1.13 1.14 1.5 2 2.5 3 3.5 4 4.5 5 5.5 vcc (v) bandgap voltage (v) 85 c 25 c -40 c 329 atmega169v/l 2514j?avr?12/03 figure 186. analog comparator offset voltage vs. common mode voltage (v cc = 5v) figure 187. analog comparator offset voltage vs. common mode voltage (v cc =2.7v) analog comparator offset voltage vs. common mode voltage v cc = 5v -0.004 -0.002 0 0.002 0.004 0.006 0.008 0 0.5 1 1.5 2 2.5 3 3.5 4 4.5 5 common mode voltage (v) comparator offset voltage (v) 85 c 25 c -40 c analog comparator offset voltage vs. common mode voltage v cc = 2.7v -0.004 -0.003 -0.002 -0.001 0 0.001 0.002 0.003 0 0.5 1 1.5 2 2.5 3 common mode voltage (v) comparator offset voltage (v) 85 c 25 c -40 c 330 atmega169v/l 2514j?avr?12/03 internal oscillator speed figure 188. watchdog oscillator frequency vs. v cc figure 189. calibrated 8 mhz rc oscillator frequency vs. temperature watchdog oscillator frequency vs. v cc 800 850 900 950 1000 1050 1100 1150 1200 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) f rc (khz) 85 c 25 c -40 c calibrated 8mhz rc oscillator frequency vs. temperature 7.2 7.4 7.6 7.8 8 8.2 8.4 8.6 8.8 -60 -40 -20 0 20 40 60 80 100 t a (?c) f rc (mhz) 5.5v 4.0v 2.7v 1.8v 331 atmega169v/l 2514j?avr?12/03 figure 190. calibrated 8 mhz rc oscillator frequency vs. v cc figure 191. calibrated 8 mhz rc oscillator frequency vs. osccal value calibrated 8mhz rc oscillator frequency vs. v cc 6 6.5 7 7.5 8 8.5 9 9.5 10 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) f rc (mhz) 85 c 25 c -40 c calibrated 8mhz rc oscillator frequency vs. osccal value 3 4 5 6 7 8 9 10 11 12 13 0 163248648096112 osccal value f rc (mhz) 332 atmega169v/l 2514j?avr?12/03 current consumption of peripheral units figure 192. brownout detector current vs. v cc figure 193. adc current vs. v cc (aref = avcc) brownout detector current vs. v cc 0 5 10 15 20 25 30 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) 25c 85c -40c adc current vs. v cc aref = av cc 0 50 100 150 200 250 300 350 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) 85 c 25 c -40 c 333 atmega169v/l 2514j?avr?12/03 figure 194. aref external reference current vs. v cc figure 195. 32 khz tosc current vs. v cc (watchdog timer disabled) aref external reference current vs. v cc 0 20 40 60 80 100 120 140 160 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i aref (ua) 85 c 25 c -40 c 32khz tosc current vs. v cc watchdog timer disabled 0 5 10 15 20 25 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) 85 c 25 c 334 atmega169v/l 2514j?avr?12/03 figure 196. watchdog timer current vs. v cc figure 197. analog comparator current vs. v cc watchdog timer current vs. v cc 0 2 4 6 8 10 12 14 16 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) 85 c 25 c -40 c analog comparator current vs. v cc 0 20 40 60 80 100 120 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) 85 c 25 c -40 c 335 atmega169v/l 2514j?avr?12/03 figure 198. programming current vs. v cc current consumption in reset and reset pulsewidth figure 199. reset supply current vs. v cc (0.1 - 1.0 mhz, excluding current through the reset pull-up) programming current vs. vcc 0 5 10 15 20 25 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ma) 85 c 25 c -40 c reset supply current vs. frequency 0.1 - 1.0 mhz, excluding current through the reset pullup 0 0.02 0.04 0.06 0.08 0.1 0.12 0.14 0.16 0.18 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 frequency (mhz) i cc (ma) 5.5v 4.5v 4.0v 3.3v 2.7v 1.8v 5.0v 336 atmega169v/l 2514j?avr?12/03 figure 200. reset supply current vs. v cc (1 - 20 mhz, excluding current through the reset pull-up) figure 201. reset pulse width vs. v cc reset supply current vs. frequency 1 - 20 mhz, excluding current through the reset pullup 0 0.5 1 1.5 2 2.5 3 3.5 02468101214161820 frequency (mhz) i cc (ma) 5.5v 4.5v 4.0v 3.3v 2.7v 1.8v 5.0v reset pulse width vs. v cc 0 500 1000 1500 2000 2500 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) pulsewidth (ns) 85 c 25 c -40 c 337 atmega169v/l 2514j?avr?12/03 register summary address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 page (0xff) reserved ? ? ? ? ? ? ? ? (0xfe) lcddr18 ? ? ? ? ? ? ? seg324 224 (0xfd) lcddr17 seg323 seg322 seg321 seg320 seg319 seg318 seg317 seg316 224 (0xfc) lcddr16 seg315 seg314 seg313 seg312 seg311 seg310 seg309 seg308 224 (0xfb) lcddr15 seg307 seg306 seg305 seg304 seg303 seg302 seg301 seg300 224 (0xfa) reserved ? ? ? ? ? ? ? ? (0xf9) lcddr13 ? ? ? ? ? ? ? seg224 224 (0xf8) lcddr12 seg223 seg222 seg221 seg220 seg219 seg218 seg217 seg216 224 (0xf7) lcddr11 seg215 seg214 seg213 seg212 seg211 seg210 seg209 seg208 224 (0xf6) lcddr10 seg207 seg206 seg205 seg204 seg203 seg202 seg201 seg200 224 (0xf5) reserved ? ? ? ? ? ? ? ? (0xf4) lcddr8 ? ? ? ? ? ? ? seg124 224 (0xf3) lcddr7 seg123 seg122 seg121 seg120 seg119 seg118 seg117 seg116 224 (0xf2) lcddr6 seg115 seg114 seg113 seg112 seg111 seg110 seg109 seg108 224 (0xf1) lcddr5 seg107 seg106 seg105 seg104 seg103 seg102 seg101 seg100 224 (0xf0) reserved ? ? ? ? ? ? ? ? (0xef) lcddr3 ? ? ? ? ? ? ? seg024 224 (0xee) lcddr2 seg023 seg022 seg021 seg020 seg019 seg018 seg017 seg016 224 (0xed) lcddr1 seg015 seg014 seg013 seg012 seg011 seg010 seg09 seg008 224 (0xec) lcddr0 seg007 seg006 seg005 seg004 seg003 seg002 seg001 seg000 224 (0xeb) reserved ? ? ? ? ? ? ? ? (0xea) reserved ? ? ? ? ? ? ? ? (0xe9) reserved ? ? ? ? ? ? ? ? (0xe8) reserved ? ? ? ? ? ? ? ? (0xe7) lcdccr ? ? ? ? lcdcc3 lcdcc2 lcdcc1 lcdcc0 224 (0xe6) lcdfrr ? lcdps2 lcdps1 lcdps0 ? lcdcd2 lcdcd1 lcdcd0 222 (0xe5) lcdcrb lcdcs lcd2b lcdmux1 lcdmux0 ? lcdpm2 lcdpm1 lcdpm0 220 (0xe4) lcdcra lcden lcdab ? lcdif lcdie ? ? lcdbl 220 (0xe3) reserved ? ? ? ? ? ? ? ? (0xe2) reserved ? ? ? ? ? ? ? ? (0xe1) reserved ? ? ? ? ? ? ? ? (0xe0) reserved ? ? ? ? ? ? ? ? (0xdf) reserved ? ? ? ? ? ? ? ? (0xde) reserved ? ? ? ? ? ? ? ? (0xdd) reserved ? ? ? ? ? ? ? ? (0xdc) reserved ? ? ? ? ? ? ? ? (0xdb) reserved ? ? ? ? ? ? ? ? (0xda) reserved ? ? ? ? ? ? ? ? (0xd9) reserved ? ? ? ? ? ? ? ? (0xd8) reserved ? ? ? ? ? ? ? ? (0xd7) reserved ? ? ? ? ? ? ? ? (0xd6) reserved ? ? ? ? ? ? ? ? (0xd5) reserved ? ? ? ? ? ? ? ? (0xd4) reserved ? ? ? ? ? ? ? ? (0xd3) reserved ? ? ? ? ? ? ? ? (0xd2) reserved ? ? ? ? ? ? ? ? (0xd1) reserved ? ? ? ? ? ? ? ? (0xd0) reserved ? ? ? ? ? ? ? ? (0xcf) reserved ? ? ? ? ? ? ? ? (0xce) reserved ? ? ? ? ? ? ? ? (0xcd) reserved ? ? ? ? ? ? ? ? (0xcc) reserved ? ? ? ? ? ? ? ? (0xcb) reserved ? ? ? ? ? ? ? ? (0xca) reserved ? ? ? ? ? ? ? ? (0xc9) reserved ? ? ? ? ? ? ? ? (0xc8) reserved ? ? ? ? ? ? ? ? (0xc7) reserved ? ? ? ? ? ? ? ? (0xc6) udr usart i/o data register 169 (0xc5) ubrrh usart baud rate register high 173 (0xc4) ubrrl usart baud rate register low 173 (0xc3) reserved ? ? ? ? ? ? ? ? (0xc2) ucsrc ? umsel upm1 upm0 usbs ucsz1 ucsz0 ucpol 169 (0xc1) ucsrb rxcie txcie udrie rxen txen ucsz2 rxb8 txb8 169 (0xc0) ucsra rxc txc udre fe dor upe u2x mpcm 169 338 atmega169v/l 2514j?avr?12/03 (0xbf) reserved ? ? ? ? ? ? ? ? (0xbe) reserved ? ? ? ? ? ? ? ? (0xbd) reserved ? ? ? ? ? ? ? ? (0xbc) reserved ? ? ? ? ? ? ? ? (0xbb) reserved ? ? ? ? ? ? ? ? (0xba) usidr usi data register 184 (0xb9) usisr usisif usioif usipf usidc usicnt3 usicnt2 usicnt1 usicnt0 185 (0xb8) usicr usisie usioie usiwm1 usiwm0 usics1 usics0 usiclk usitc 186 (0xb7) reserved ? ? ? ? ? ? ? (0xb6) assr ? ? ? exclk as2 tcn2ub ocr2ub tcr2ub 138 (0xb5) reserved ? ? ? ? ? ? ? ? (0xb4) reserved ? ? ? ? ? ? ? ? (0xb3) ocr2a timer/counter2 output compare register a 137 (0xb2) tcnt2 timer/counter2 (8-bit) 137 (0xb1) reserved ? ? ? ? ? ? ? ? (0xb0) tccr2a foc2a wgm20 com2a1 com2a0 wgm21 cs22 cs21 cs20 135 (0xaf) reserved ? ? ? ? ? ? ? ? (0xae) reserved ? ? ? ? ? ? ? ? (0xad) reserved ? ? ? ? ? ? ? ? (0xac) reserved ? ? ? ? ? ? ? ? (0xab) reserved ? ? ? ? ? ? ? ? (0xaa) reserved ? ? ? ? ? ? ? ? (0xa9) reserved ? ? ? ? ? ? ? ? (0xa8) reserved ? ? ? ? ? ? ? ? (0xa7) reserved ? ? ? ? ? ? ? ? (0xa6) reserved ? ? ? ? ? ? ? ? (0xa5) reserved ? ? ? ? ? ? ? ? (0xa4) reserved ? ? ? ? ? ? ? ? (0xa3) reserved ? ? ? ? ? ? ? ? (0xa2) reserved ? ? ? ? ? ? ? ? (0xa1) reserved ? ? ? ? ? ? ? ? (0xa0) reserved ? ? ? ? ? ? ? ? (0x9f) reserved ? ? ? ? ? ? ? ? (0x9e) reserved ? ? ? ? ? ? ? ? (0x9d) reserved ? ? ? ? ? ? ? ? (0x9c) reserved ? ? ? ? ? ? ? ? (0x9b) reserved ? ? ? ? ? ? ? ? (0x9a) reserved ? ? ? ? ? ? ? ? (0x99) reserved ? ? ? ? ? ? ? ? (0x98) reserved ? ? ? ? ? ? ? ? (0x97) reserved ? ? ? ? ? ? ? ? (0x96) reserved ? ? ? ? ? ? ? ? (0x95) reserved ? ? ? ? ? ? ? ? (0x94) reserved ? ? ? ? ? ? ? ? (0x93) reserved ? ? ? ? ? ? ? ? (0x92) reserved ? ? ? ? ? ? ? ? (0x91) reserved ? ? ? ? ? ? ? ? (0x90) reserved ? ? ? ? ? ? ? ? (0x8f) reserved ? ? ? ? ? ? ? ? (0x8e) reserved ? ? ? ? ? ? ? ? (0x8d) reserved ? ? ? ? ? ? ? ? (0x8c) reserved ? ? ? ? ? ? ? ? (0x8b) ocr1bh timer/counter1 - output compare register b high byte 121 (0x8a) ocr1bl timer/counter1 - output compare register b low byte 121 (0x89) ocr1ah timer/counter1 - output compare register a high byte 121 (0x88) ocr1al timer/counter1 - output compare register a low byte 121 (0x87) icr1h timer/counter1 - input capture register high byte 122 (0x86) icr1l timer/counter1 - input capture register low byte 122 (0x85) tcnt1h timer/counter1 - counter register high byte 121 (0x84) tcnt1l timer/counter1 - counter register low byte 121 (0x83) reserved ? ? ? ? ? ? ? ? (0x82) tccr1c foc1a foc1b ? ? ? ? ? ?120 (0x81) tccr1b icnc1 ices1 ? wgm13 wgm12 cs12 cs11 cs10 119 (0x80) tccr1a com1a1 com1a0 com1b1 com1b0 ? ?wgm11wgm10 117 (0x7f) didr1 ? ? ? ? ? ? ain1d ain0d 191 (0x7e) didr0 adc7d adc6d adc5d adc4d adc3d adc2d adc1d adc0d 209 address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 page 339 atmega169v/l 2514j?avr?12/03 (0x7d) reserved ? ? ? ? ? ? ? ? (0x7c) admux refs1 refs0 adlar mux4 mux3 mux2 mux1 mux0 205 (0x7b) adcsrb ?acme ? ? ? adts2 adts1 adts0 189, 209 (0x7a) adcsra aden adsc adate adif adie adps2 adps1 adps0 207 (0x79) adch adc data register high byte 208 (0x78) adcl adc data register low byte 208 (0x77) reserved ? ? ? ? ? ? ? ? (0x76) reserved ? ? ? ? ? ? ? ? (0x75) reserved ? ? ? ? ? ? ? ? (0x74) reserved ? ? ? ? ? ? ? ? (0x73) reserved ? ? ? ? ? ? ? ? (0x72) reserved ? ? ? ? ? ? ? ? (0x71) reserved ? ? ? ? ? ? ? ? (0x70) timsk2 ? ? ? ? ? ? ocie2a toie2 140 (0x6f) timsk1 ? ?icie1 ? ? ocie1b ocie1a toie1 122 (0x6e) timsk0 ? ? ? ? ? ? ocie0a toie0 92 (0x6d) reserved ? ? ? ? ? ? ? ? (0x6c) pcmsk1 pcint15 pcint14 pcint13 pcint12 pcint11 pcint10 pcint9 pcint8 78 (0x6b) pcmsk0 pcint7 pcint6 pcint5 pcint4 pcint3 pcint2 pcint1 pcint0 78 (0x6a) reserved ? ? ? ? ? ? ? ? (0x69) eicra ? ? ? ? ? ?isc01isc00 76 (0x68) reserved ? ? ? ? ? ? ? ? (0x67) reserved ? ? ? ? ? ? ? ? (0x66) osccal oscillator calibration register 28 (0x65) reserved ? ? ? ? ? ? ? ? (0x64) reserved ? ? ? ? ? ? ? ? (0x63) reserved ? ? ? ? ? ? ? ? (0x62) reserved ? ? ? ? ? ? ? ? (0x61) clkpr clkpce ? ? ? clkps3 clkps2 clkps1 clkps0 30 (0x60) wdtcr ? ? ? wdce wde wdp2 wdp1 wdp0 43 0x3f (0x5f) sreg i t h s v n z c 9 0x3e (0x5e) sph sp15 sp14 sp13 sp12 sp11 sp10 sp9 sp8 11 0x3d (0x5d) spl sp7 sp6 sp5 sp4 sp3 sp2 sp1 sp0 11 0x3c (0x5c) reserved 0x3b (0x5b) reserved 0x3a (0x5a) reserved 0x39 (0x59) reserved 0x38 (0x58) reserved 0x37 (0x57) spmcsr spmie rwwsb ? rwwsre blbset pgwrt pgers spmen 257 0x36 (0x56) reserved ? ? ? ? ? ? ? ? 0x35 (0x55) mcucr jtd ? ?pud ? ? ivsel ivce 236 0x34 (0x54) mcusr ? ? ? jtrf wdrfborfextrf porf 236 0x33 (0x53) smcr ? ? ? ? sm2 sm1 sm0 se 32 0x32 (0x52) reserved ? ? ? ? ? ? ? ? 0x31 (0x51) ocdr idrd/ocd ocdr6 ocdr5 ocdr4 ocdr3 ocdr2 ocdr1 ocdr0 231 0x30 (0x50) acsr acd acbg aco aci acie acic acis1 acis0 189 0x2f (0x4f) reserved ? ? ? ? ? ? ? ? 0x2e (0x4e) spdr spi data register 149 0x2d (0x4d) spsr spif wcol ? ? ? ? ?spi2x 149 0x2c (0x4c) spcr spie spe dord mstr cpol cpha spr1 spr0 147 0x2b (0x4b) gpior2 general purpose i/o register 2 22 0x2a (0x4a) gpior1 general purpose i/o register 1 22 0x29 (0x49) reserved ? ? ? ? ? ? ? ? 0x28 (0x48) reserved ? ? ? ? ? ? ? ? 0x27 (0x47) ocr0a timer/counter0 output compare register a 92 0x26 (0x46) tcnt0 timer/counter0 (8 bit) 91 0x25 (0x45) reserved ? ? ? ? ? ? ? ? 0x24 (0x44) tccr0a foc0a wgm00 com0a1 com0a0 wgm01 cs02 cs01 cs00 89 0x23 (0x43) gtccr tsm ? ? ? ? ? psr2 psr10 94 0x22 (0x42) eearh ? ? ? ? ? ? ? eear8 18 0x21 (0x41) eearl eeprom address register low byte 18 0x20 (0x40) eedr eeprom data register 18 0x1f (0x3f) eecr ? ? ? ? eerie eemwe eewe eere 18 0x1e (0x3e) gpior0 general purpose i/o register 0 22 0x1d (0x3d) eimsk pcie1 pcie0 ? ? ? ? ?int0 77 0x1c (0x3c) eifr pcif1 pcif0 ? ? ? ? ? intf0 77 address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 page 340 atmega169v/l 2514j?avr?12/03 note: 1. for compatibility with future devices, reserved bits should be written to zero if accessed. reserved i/o memory addresse s should never be written. 2. i/o registers within the address range 0x00 - 0x1f are directly bit-accessible using the sbi and cbi instructions. in these registers, the value of single bits can be checked by using the sbis and sbic instructions. 3. some of the status flags are cleared by writing a logical one to them. note that, unlike most other avrs, the cbi and sbi instructions will only operate on the specified bit, and can therefore be used on registers containing such status flags. the cbi and sbi instructions work with registers 0x00 to 0x1f only. 4. when using the i/o specific commands in and out, the i/o addresses 0x00 - 0x3f must be used. when addressing i/o registers as data space using ld and st instructions, 0x20 must be added to these addresses. the atmega169 is a com- plex microcontroller with more peripheral units than can be supported within the 64 location reserved in opcode for the in and out instructions. for the extended i/o space from 0x60 - 0xff in sram, only the st/sts/std and ld/lds/ldd instructions can be used. 0x1b (0x3b) reserved ? ? ? ? ? ? ? ? 0x1a (0x3a) reserved ? ? ? ? ? ? ? ? 0x19 (0x39) reserved ? ? ? ? ? ? ? ? 0x18 (0x38) reserved ? ? ? ? ? ? ? ? 0x17 (0x37) tifr2 ? ? ? ? ? ? ocf2a tov2 141 0x16 (0x36) tifr1 ? ?icf1 ? ? ocf1b ocf1a tov1 123 0x15 (0x35) tifr0 ? ? ? ? ? ?ocf0atov0 92 0x14 (0x34) portg ? ? ? portg4 portg3 portg2 portg1 portg0 75 0x13 (0x33) ddrg ? ? ? ddg4 ddg3 ddg2 ddg1 ddg0 75 0x12 (0x32) ping ? ? ping5 ping4 ping3 ping2 ping1 ping0 75 0x11 (0x31) portf portf7 portf6 portf5 portf4 portf3 portf2 portf1 portf0 74 0x10 (0x30) ddrf ddf7 ddf6 ddf5 ddf4 ddf3 ddf2 ddf1 ddf0 74 0x0f (0x2f) pinf pinf7 pinf6 pinf5 pinf4 pinf3 pinf2 pinf1 pinf0 75 0x0e (0x2e) porte porte7 porte6 porte5 porte4 porte3 porte2 porte1 porte0 74 0x0d (0x2d) ddre dde7 dde6 dde5 dde4 dde3 dde2 dde1 dde0 74 0x0c (0x2c) pine pine7 pine6 pine5 pine4 pine3 pine2 pine1 pine0 74 0x0b (0x2b) portd portd7 portd6 portd5 portd4 portd3 portd2 portd1 portd0 74 0x0a (0x2a) ddrd ddd7 ddd6 ddd5 ddd4 ddd3 ddd2 ddd1 ddd0 74 0x09 (0x29) pind pind7 pind6 pind5 pind4 pind3 pind2 pind1 pind0 74 0x08 (0x28) portc portc7 portc6 portc5 portc4 portc3 portc2 portc1 portc0 73 0x07 (0x27) ddrc ddc7 ddc6 ddc5 ddc4 ddc3 ddc2 ddc1 ddc0 73 0x06 (0x26) pinc pinc7 pinc6 pinc5 pinc4 pinc3 pinc2 pinc1 pinc0 74 0x05 (0x25) portb portb7 portb6 portb5 portb4 portb3 portb2 portb1 portb0 73 0x04 (0x24) ddrb ddb7 ddb6 ddb5 ddb4 ddb3 ddb2 ddb1 ddb0 73 0x03 (0x23) pinb pinb7 pinb6 pinb5 pinb4 pinb3 pinb2 pinb1 pinb0 73 0x02 (0x22) porta porta7 porta6 porta5 porta4 porta3 porta2 porta1 porta0 73 0x01 (0x21) ddra dda7 dda6 dda5 dda4 dda3 dda2 dda1 dda0 73 0x00 (0x20) pina pina7 pina6 pina5 pina4 pina3 pina2 pina1 pina0 73 address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 page 341 atmega169v/l 2514j?avr?12/03 instruction set summary mnemonics operands description operation flags #clocks arithmetic and logic instructions add rd, rr add two registers rd rd + rr z,c,n,v,h 1 adc rd, rr add with carry two registers rd rd + rr + c z,c,n,v,h 1 adiw rdl,k add immediate to word rdh:rdl rdh:rdl + k z,c,n,v,s 2 sub rd, rr subtract two registers rd rd - rr z,c,n,v,h 1 subi rd, k subtract constant from register rd rd - k z,c,n,v,h 1 sbc rd, rr subtract with carry two registers rd rd - rr - c z,c,n,v,h 1 sbci rd, k subtract with carry constant from reg. rd rd - k - c z,c,n,v,h 1 sbiw rdl,k subtract immediate from word rdh:rdl rdh:rdl - k z,c,n,v,s 2 and rd, rr logical and registers rd rd ? rr z,n,v 1 andi rd, k logical and register and constant rd rd ? kz,n,v1 or rd, rr logical or registers rd rd v rr z,n,v 1 ori rd, k logical or register and constant rd rd v k z,n,v 1 eor rd, rr exclusive or registers rd rd rr z,n,v 1 com rd one?s complement rd 0xff ? rd z,c,n,v 1 neg rd two?s complement rd 0x00 ? rd z,c,n,v,h 1 sbr rd,k set bit(s) in register rd rd v k z,n,v 1 cbr rd,k clear bit(s) in register rd rd ? (0xff - k) z,n,v 1 inc rd increment rd rd + 1 z,n,v 1 dec rd decrement rd rd ? 1 z,n,v 1 tst rd test for zero or minus rd rd ? rd z,n,v 1 clr rd clear register rd rd rd z,n,v 1 ser rd set register rd 0xff none 1 mul rd, rr multiply unsigned r1:r0 rd x rr z,c 2 muls rd, rr multiply signed r1:r0 rd x rr z,c 2 mulsu rd, rr multiply signed with unsigned r1:r0 rd x rr z,c 2 fmul rd, rr fractional multiply unsigned r1:r0 (rd x rr) << 1 z,c 2 fmuls rd, rr fractional multiply signed r1:r0 (rd x rr) << 1 z,c 2 fmulsu rd, rr fractional multiply signed with unsigned r1:r0 (rd x rr) << 1 z,c 2 branch instructions rjmp k relative jump pc pc + k + 1 none 2 ijmp indirect jump to (z) pc z none 2 jmp k direct jump pc knone3 rcall k relative subroutine call pc pc + k + 1 none 3 icall indirect call to (z) pc znone3 call k direct subroutine call pc knone4 ret subroutine return pc stack none 4 reti interrupt return pc stack i 4 cpse rd,rr compare, skip if equal if (rd = rr) pc pc + 2 or 3 none 1/2/3 cp rd,rr compare rd ? rr z, n,v,c,h 1 cpc rd,rr compare with carry rd ? rr ? c z, n,v,c,h 1 cpi rd,k compare register with immediate rd ? k z, n,v,c,h 1 sbrc rr, b skip if bit in register cleared if (rr(b)=0) pc pc + 2 or 3 none 1/2/3 sbrs rr, b skip if bit in register is set if (rr(b)=1) pc pc + 2 or 3 none 1/2/3 sbic p, b skip if bit in i/o register cleared if (p(b)=0) pc pc + 2 or 3 none 1/2/3 sbis p, b skip if bit in i/o register is set if (p(b)=1) pc pc + 2 or 3 none 1/2/3 brbs s, k branch if status flag set if (sreg(s) = 1) then pc pc+k + 1 none 1/2 brbc s, k branch if status flag cleared if (sreg(s) = 0) then pc pc+k + 1 none 1/2 breq k branch if equal if (z = 1) then pc pc + k + 1 none 1/2 brne k branch if not equal if (z = 0) then pc pc + k + 1 none 1/2 brcs k branch if carry set if (c = 1) then pc pc + k + 1 none 1/2 brcc k branch if carry cleared if (c = 0) then pc pc + k + 1 none 1/2 brsh k branch if same or higher if (c = 0) then pc pc + k + 1 none 1/2 brlo k branch if lower if (c = 1) then pc pc + k + 1 none 1/2 brmi k branch if minus if (n = 1) then pc pc + k + 1 none 1/2 brpl k branch if plus if (n = 0) then pc pc + k + 1 none 1/2 brge k branch if greater or equal, signed if (n v= 0) then pc pc + k + 1 none 1/2 brlt k branch if less than zero, signed if (n v= 1) then pc pc + k + 1 none 1/2 brhs k branch if half carry flag set if (h = 1) then pc pc + k + 1 none 1/2 brhc k branch if half carry flag cleared if (h = 0) then pc pc + k + 1 none 1/2 brts k branch if t flag set if (t = 1) then pc pc + k + 1 none 1/2 brtc k branch if t flag cleared if (t = 0) then pc pc + k + 1 none 1/2 brvs k branch if overflow flag is set if (v = 1) then pc pc + k + 1 none 1/2 brvc k branch if overflow flag is cleared if (v = 0) then pc pc + k + 1 none 1/2 342 atmega169v/l 2514j?avr?12/03 brie k branch if interrupt enabled if ( i = 1) then pc pc + k + 1 none 1/2 brid k branch if interrupt disabled if ( i = 0) then pc pc + k + 1 none 1/2 bit and bit-test instructions sbi p,b set bit in i/o register i/o(p,b) 1none2 cbi p,b clear bit in i/o register i/o(p,b) 0none2 lsl rd logical shift left rd(n+1) rd(n), rd(0) 0 z,c,n,v 1 lsr rd logical shift right rd(n) rd(n+1), rd(7) 0 z,c,n,v 1 rol rd rotate left through carry rd(0) c,rd(n+1) rd(n),c rd(7) z,c,n,v 1 ror rd rotate right through carry rd(7) c,rd(n) rd(n+1),c rd(0) z,c,n,v 1 asr rd arithmetic shift right rd(n) rd(n+1), n=0..6 z,c,n,v 1 swap rd swap nibbles rd(3..0) rd(7..4),rd(7..4) rd(3..0) none 1 bset s flag set sreg(s) 1sreg(s)1 bclr s flag clear sreg(s) 0 sreg(s) 1 bst rr, b bit store from register to t t rr(b) t 1 bld rd, b bit load from t to register rd(b) tnone1 sec set carry c 1c1 clc clear carry c 0 c 1 sen set negative flag n 1n1 cln clear negative flag n 0 n 1 sez set zero flag z 1z1 clz clear zero flag z 0 z 1 sei global interrupt enable i 1i1 cli global interrupt disable i 0 i 1 ses set signed test flag s 1s1 cls clear signed test flag s 0 s 1 sev set twos complement overflow. v 1v1 clv clear twos complement overflow v 0 v 1 set set t in sreg t 1t1 clt clear t in sreg t 0 t 1 seh set half carry flag in sreg h 1h1 clh clear half carry flag in sreg h 0 h 1 data transfer instructions mov rd, rr move between registers rd rr none 1 movw rd, rr copy register word rd+1:rd rr+1:rr none 1 ldi rd, k load immediate rd knone1 ld rd, x load indirect rd (x) none 2 ld rd, x+ load indirect and post-inc. rd (x), x x + 1 none 2 ld rd, - x load indirect and pre-dec. x x - 1, rd (x) none 2 ld rd, y load indirect rd (y) none 2 ld rd, y+ load indirect and post-inc. rd (y), y y + 1 none 2 ld rd, - y load indirect and pre-dec. y y - 1, rd (y) none 2 ldd rd,y+q load indirect with displacement rd (y + q) none 2 ld rd, z load indirect rd (z) none 2 ld rd, z+ load indirect and post-inc. rd (z), z z+1 none 2 ld rd, -z load indirect and pre-dec. z z - 1, rd (z) none 2 ldd rd, z+q load indirect with displacement rd (z + q) none 2 lds rd, k load direct from sram rd (k) none 2 st x, rr store indirect (x) rr none 2 st x+, rr store indirect and post-inc. (x) rr, x x + 1 none 2 st - x, rr store indirect and pre-dec. x x - 1, (x) rr none 2 st y, rr store indirect (y) rr none 2 st y+, rr store indirect and post-inc. (y) rr, y y + 1 none 2 st - y, rr store indirect and pre-dec. y y - 1, (y) rr none 2 std y+q,rr store indirect with displacement (y + q) rr none 2 st z, rr store indirect (z) rr none 2 st z+, rr store indirect and post-inc. (z) rr, z z + 1 none 2 st -z, rr store indirect and pre-dec. z z - 1, (z) rr none 2 std z+q,rr store indirect with displacement (z + q) rr none 2 sts k, rr store direct to sram (k) rr none 2 lpm load program memory r0 (z) none 3 lpm rd, z load program memory rd (z) none 3 lpm rd, z+ load program memory and post-inc rd (z), z z+1 none 3 spm store program memory (z) r1:r0 none - in rd, p in port rd pnone1 out p, rr out port p rr none 1 push rr push register on stack stack rr none 2 mnemonics operands description operation flags #clocks 343 atmega169v/l 2514j?avr?12/03 pop rd pop register from stack rd stack none 2 mcu control instructions nop no operation none 1 sleep sleep (see specific descr. for sleep function) none 1 wdr watchdog reset (see specific descr. for wdr/timer) none 1 break break for on-chip debug only none n/a mnemonics operands description operation flags #clocks 344 atmega169v/l 2514j?avr?12/03 ordering information note: this device can also be supplied in wafer form. please contact your local atmel sales office for detailed ordering informa tion and minimum quantities. speed (mhz) power supply ordering code package operation range 1 1.8 - 5.5v ATMEGA169V-1AI atmega169v-1mi 64a 64m1 industrial (-4 0 c to 85 c) 8 2.7 - 5.5v atmega169l-8ai atmega169l-8mi 64a 64m1 industrial (-4 0 c to 85 c) 16 4.5 - 5.5v atmega169-16ai atmega169-16mi 64a 64m1 industrial (-4 0 c to 85 c) package type 64a 64-lead, thin (1.0 mm) plastic gull wing quad flat package (tqfp) 64m1 64-pad, 9 x 9 x 1.0 mm body, lead pitch 0.50 mm, micro lead frame package (mlf) 345 atmega169v/l 2514j?avr?12/03 packaging information 64a 2325 orchard parkway san jose, ca 95131 title drawing no. r rev. 64a, 64-lead, 14 x 14 mm body size, 1.0 mm body thickness, 0.8 mm lead pitch, thin profile plastic quad flat package (tqfp) b 64a 10/5/2001 pin 1 identifier 0?~7? pin 1 l c a1 a2 a d1 d e e1 e b common dimensions (unit of measure = mm) symbol min nom max note notes: 1. this package conforms to jedec reference ms-026, variation aeb. 2. dimensions d1 and e1 do not include mold protrusion. allowable protrusion is 0.25 mm per side. dimensions d1 and e1 are maximum plastic body size dimensions including mold mismatch. 3. lead coplanarity is 0.10 mm maximum. a 1.20 a1 0.05 0.15 a2 0.95 1.00 1.05 d 15.75 16.00 16.25 d1 13.90 14.00 14.10 note 2 e 15.75 16.00 16.25 e1 13.90 14.00 14.10 note 2 b 0.30 0.45 c 0.09 0.20 l 0.45 0.75 e 0.80 typ 346 atmega169v/l 2514j?avr?12/03 64m1 2325 orchard parkway san jose, ca 95131 title drawing no. r rev. 64m1 , 64-pad, 9 x 9 x 1.0 mm body, lead pitch 0.50 mm micro lead frame package (mlf) c 64m1 01/15/03 common dimensions (unit of measure = mm) symbol min nom max note a 0.80 0.90 1.00 a1 ? 0.02 0.05 b 0.23 0.25 0.28 d 9.00 bsc d2 5.20 5.40 5.60 e 9.00 bsc e2 5.20 5.40 5.60 e 0.50 bsc l 0.35 0.40 0.45 notes: 1. jedec standard mo-220, fig. 1, vmmd. top view side view bottom view d e marked pin# 1 id e2 d2 b e pin #1 corner l seating plane a1 c a 1 2 3 c 0.08 347 atmega169v/l 2514j?avr?12/03 errata atmega169 rev d high serial resistance in the glass can result in dim segments on the lcd idcode masks data from tdi input 2. high serial resistance in the glass can result in dim segments on the lcd some display types with high serial resistance (>20 k ? ) inside the glass can result in dim segments on the lcd problem fix/workaround add a 1 nf (0.47 - 1.5 nf) capacitor between each common pin and ground. 1. idcode masks data from tdi input the jtag instruction idcode is not working correctly. data to succeeding devices are replaced by all-ones during update-dr. problem fix / workaround ? if atmega169 is the only device in the scan chain, the problem is not visible. ? select the device id register of the atmega169 by issuing the idcode instruction or by entering the test-logic-reset state of the tap controller to read out the contents of its device id register and possibly data from succeeding devices of the scan chain. issue the bypass instruction to the atmega169 while reading the device id registers of preceding devices of the boundary scan chain. ? if the device ids of all devices in the boundary scan chain must be captured simultaneously, the atmega169 must be the fist device in the chain. atmega169 rev c high current consumption in power down when jtagen is programmed lcd contrast control some data combinations can result in dim segments on the lcd lcd current consumption idcode masks data from tdi input 5. high current consumption in power down when jtagen is programmed the input buffer on tdo (pf6) is always enabled and the pull-up is always disabled when jtag is programmed. this can leave the output floating. problem fix/workaround add external pull-up to pf6. unprogram the jtagen fuse before shipping out the end product. 4. lcd contrast control the contrast control is not working properly when using synchronous clock (chip clock) to obtain an lcd clock, and the chip clock is 125 khz or faster. problem fix/workaround use a low chip clock frequency (32 khz) or apply an external voltage to the lcd- cap pin. 3. some data combinations can result in dim segments on the lcd all segments connected to a common plane might be dimmed (lower contrast) when a certain combination of data is displayed. problem fix/workaround 348 atmega169v/l 2514j?avr?12/03 default waveform: if there are any unused segment pins, loading one of these with a 1 nf capacitor and always write ?0? to this segment eliminates the problem. low power waveform: add a 1 nf capacitor to each common pin. 2. lcd current consumption in an interval where v cc is within the range vlcd -0.2v to vlcd + 0.4v, the lcd current consumption is up to three times higher than expected. this will only be an issue in power-save mode with the lcd running as the lcd current is negligible compared to the overall power consumption in all other modes of operation. problem fix/workaround no known workaround. 1. idcode masks data from tdi input the jtag instruction idcode is not working correctly. data to succeeding devices are replaced by all-ones during update-dr. problem fix / workaround ? if atmega169 is the only device in the scan chain, the problem is not visible. ? select the device id register of the atmega169 by issuing the idcode instruction or by entering the test-logic-reset state of the tap controller to read out the contents of its device id register and possibly data from succeeding devices of the scan chain. issue the bypass instruction to the atmega169 while reading the device id registers of preceding devices of the boundary scan chain. ? if the device ids of all devices in the boundary scan chain must be captured simultaneously, the atmega169 must be the fist device in the chain. atmega169 rev b internal oscillator runs at 4 mhz lcd contrast voltage is not correct external oscillator is non-functional usart adc measures with lower accuracy than specified serial downloading idcode masks data from tdi input 7. internal oscillator runs at 4 mhz the internal oscillator runs at 4 mhz inst ead of the specified 8 mhz. therefore, all flash/eeprom programming times are twice as long as specified. this includes chip erase, byte programming, page programming, fuse programming, lock bit programming, eeprom write from the cpu, and flash self-programming. for this reason, rev-b samples are shipped with the ckdiv8 fuse unprogrammed. problem fix/workaround if 8 mhz operation is required, apply an external clock (this will be fixed in rev. c). 6. lcd contrast voltage is not correct the lcd contrast voltage between 1.8v and 3.1v is incorrect. when the v cc is between 1.8v and 3.1v, the lcd contrast voltage drops approx. 0.5v. the current consumption in this interval is higher than expected. problem fix/workaround contrast will be wrong, but display will still be readable, can be partly compensated for using the contrast control register (this will be fixed in rev. c). 349 atmega169v/l 2514j?avr?12/03 5. external oscillator is non-functional the external oscillator does not run with the setup described in the datasheet. problem fix/workaround use other clock source (this will be fixed in rev. c). alternative problem fix/workaround adding a pull-down on xtal1 will start the oscillator. 4. usart writing txen to zero during transmission causes the transmission to suddenly stop. the datasheet description tells that the transmission should complete before stop- ping the usart when txen is written to zero. problem fix/workaround ensure that the transmission is complete before writing txen to zero (this will be fixed in rev. c). 3. adc measures with lower accuracy than specified the adc does not work as intended. there is a positive offset in the result. problem fix/workaround this will be fixed in rev. c. 2. serial downloading when entering serial programming mode the second byte will not echo back as described in the serial programming algorithm. problem fix/workaround check if the third byte echoes back to ensure that the device is in programming mode (this will be fixed in rev. c). 1. idcode masks data from tdi input the jtag instruction idcode is not working correctly. data to succeeding devices are replaced by all-ones during update-dr. problem fix / workaround ? if atmega169 is the only device in the scan chain, the problem is not visible. ? select the device id register of the atmega169 by issuing the idcode instruction or by entering the test-logic-reset state of the tap controller to read out the contents of its device id register and possibly data from succeeding devices of the scan chain. issue the bypass instruction to the atmega169 while reading the device id registers of preceding devices of the boundary scan chain. ? if the device ids of all devices in the boundary scan chain must be captured simultaneously, the atmega169 must be the fist device in the chain. 350 atmega169v/l 2514j?avr?12/03 datasheet change log for atmega169 please note that the referring page numbers in this section are referring to this docu- ment. the referring revision in this section are referring to the document revision. changes from rev. 2514i-09/03 to rev. 2514j-12/03 1. updated ?calibrated internal rc oscillator? on page 27. changes from rev. 2514h-05/03 to rev. 2514i-09/03 1. removed ?advance information? from the datasheet. 2. removed agnd from figure 2 on page 3 and added ?system clock prescaler? to figure 11 on page 23. 3. updated table 16 on page 37, table 17 on page 39, table 19 on page 41 and table 40 on page 69. 4. renamed and updated ?on-chip debug system? to ?jtag interface and on-chip debug system? on page 35. 5. updated com01:0 to com0a1:0 in ?timer/counter control register a ? tccr0a? on page 89 and com21:0 to com2a1:0 in ?timer/counter control register a? tccr2a? on page 135. 6. updated ?test access port ? tap? on page 226 regarding jtagen. 7. updated description for the jtd bit on page 236. 8. added a note regarding jtagen fuse to table 119 on page 268. 9. updated absolute maximum ratings* and dc characteristics in ?electrical characteristics? on page 298. 10. updated ?errata? on page 347 and added a proposal for solving problems regarding the jtag instruction idcode. changes from rev. 2514g-04/03 to rev. 2514h-05/03 1. updated typo in figure 145, figure 165, and figure 192. changes from rev. 2514f-04/03 to rev. 2514g-04/03 1. updated ?atmega169 typical characteristics ? preliminary data? on page 304. 2. updated typo in ?ordering information? on page 344. 3. updated figure 45 on page 109, table 18 on page 39, and table 100 on page 233. changes from rev. 2514e-02/03 to rev. 2514f-04/03 1. renamed icp to icp1 in whole document. 2. removed note on ?crystal oscillator operating modes? on page 25. 351 atmega169v/l 2514j?avr?12/03 3. xtal1/xtal2 can be used as timer oscillator pins, described in chapter ?cal- ibrated internal rc oscillator? on page 27. 4. switching between prescaler settings in ?switching time? on page 31. 5. updated dc and acd characteristics in chapter ?electrical characteristics? on page 298 are updated. removed tbd?s from table 16 on page 37, table 19 on page 41, table 133 on page 300. 6. updated figure 22 on page 52, figure 25 on page 57 and figure 109 on page 238 regarding write pinx register. 7. updated ?alternate functions of port f? on page 69 regarding jtag. 8. replaced timer0 overflow with timer/counter0 compare match in ?universal serial interface ? usi? on page 178. also updated ?start condition detector? on page 184 and ?usi control register ? usicr? on page 186. 9. updated features for ?analog to digital converter? on page 192 and table 88 on page 205. 10. added notes on figure 117 on page 259 and table 118 on page 267. changes from rev. 2514d-01/03 to rev. 2514e-02/03 1. updated the section ?features? on page 1 with information regarding atmega169 and atmega169l. 2. removed all references to the pg5 pin in figure 1 on page 2, figure 2 on page 3, ?port g (pg4..pg0)? on page 6, ?alternate functions of port g? on page 71, and ?register description for i/o-ports? on page 73. 3. updated table 118, ?extended fuse byte,? on page 267. 4. added errata for ?datasheet change log for atmega169? on page 350, including ?significant data sheet changes?. 5. updated the ?ordering information? on page 344 to include the new speed grade for atmega169l and the new 16 mhz atmega169. changes from rev. 2514c-11/02 to rev. 2514d-01/03 1. added tck frequency limit in ?programming via the jtag interface? on page 285. 2. added chip erase as a first step in ?programming the flash? on page 295 and ?programming the eeprom? on page 296. 3. added the section ?unconnected pins? on page 56. 4. added tips on how to disable the ocd system in ?on-chip debug system? on page 35. 5. corrected interrupt addresses. adc and ana_comp had swapped places. 6. improved the table in ?spi timing characteristics? on page 300 and removed the table in ?spi serial programming characteristics? on page 285. 352 atmega169v/l 2514j?avr?12/03 7. changed ?will be ignored? to ?must be written to zero? for unused z-pointer bits in ?performing a page write? on page 260. 8. corrected ?lcd frame complete? to ?lcd start of frame? in the lcdcra register description on page 220. 9. changed out to sts and in to lds in usi code examples, and corrected f sckmax . the usi i/o registers are in the extended i/o space, so in and out cannot be used. lds and sts take one more cycle when executed, so f sckmax had to be changed accordingly. 10. removed toskon and tosck from table 103 on page 239, and g10 and g20 from figure 114 on page 241 and table 105 on page 242, because these sig- nals do not exist in boundary scan. 11. changed from 4 to 16 mips and mhz in the device features list. 12. corrected port a to port f in ?avcc? on page 6 under ?pin descriptions? on page 5. 13. corrected 230.4 mbps to 230.4 kbps in ?examples of baud rate setting? on page 174. 14. corrected placing of falling and rising xck edges in table 78, ?ucpol bit settings,? on page 173. 15. removed reference to multipurpose oscillator application note, which does not exist. 16. corrected number of calibrated rc oscillator cycles in table 1 on page 19 from 8,448 to 67,584. 17. various minor timer1 corrections. 18. added information about pwm symmetry for timer0 and timer2. 19. corrected the contents of didr0 and didr1. 20. made all bit names in the lcddr registers unique by adding the com num- ber digit in front of the two digits already there, e.g. seg304. 21. changed extended standby to adc noise reduction mode under ?asynchro- nous operation of timer/counter2? on page 139. 22. added note about port b having better driving capabilities than the other ports. as a consequence the table, ?dc characteristics? on page 298 was cor- rected as well. 23. added note under ?filling the temporary buffer (page loading)? on page 260 about writing to the eeprom during an spm page load. 24. removed adhsm completely. 25. updated ?packaging information? on page 345. 353 atmega169v/l 2514j?avr?12/03 changes from rev. 2514b-09/02 to rev. 2514c-11/02 1. added ?errata? on page 347. 2. added information for the 64-pad mlf package in ?ordering information? on page 344 and ?packaging information? on page 345. 3. changed temperature range and removed industrial ordering codes in ?packaging information? on page 345. changes from rev. 2514a-08/02 to rev. 2514b-09/02 1. changed the endurance on the flash to 10,000 write/erase cycles. 354 atmega169v/l 2514j?avr?12/03 i atmega169v/l 2514j?avr?12/03 table of contents features................................................................................................ 1 pin configurations............................................................................... 2 disclaimer ............................................................................................................. 2 overview............................................................................................... 3 block diagram ...................................................................................................... 3 pin descriptions.................................................................................................... 5 about code examples......................................................................... 6 avr cpu core ..................................................................................... 7 introduction ........................................................................................................... 7 architectural overview.......................................................................................... 7 alu ? arithmetic logic unit.................................................................................. 8 status register ..................................................................................................... 9 general purpose register file ........................................................................... 10 stack pointer ...................................................................................................... 11 instruction execution timing............................................................................... 12 reset and interrupt handling.............................................................................. 12 avr atmega169 memories .............................................................. 15 in-system reprogrammable flash program memory ........................................ 15 sram data memory........................................................................................... 16 eeprom data memory...................................................................................... 17 i/o memory ......................................................................................................... 22 system clock and clock options .................................................... 23 clock systems and their distribution .................................................................. 23 clock sources..................................................................................................... 24 default clock source .......................................................................................... 24 crystal oscillator................................................................................................. 25 low-frequency crystal oscillator ........................................................................ 26 calibrated internal rc oscillator ........................................................................ 27 external clock..................................................................................................... 29 clock output buffer ............................................................................................ 29 timer/counter oscillator..................................................................................... 30 system clock prescaler...................................................................................... 30 power management and sleep modes............................................. 32 idle mode ............................................................................................................ 33 adc noise reduction mode............................................................................... 33 power-down mode.............................................................................................. 33 power-save mode............................................................................................... 33 standby mode..................................................................................................... 34 minimizing power consumption ......................................................................... 34 ii atmega169v/l 2514j?avr?12/03 system control and reset ................................................................ 36 internal voltage reference ................................................................................. 41 watchdog timer ................................................................................................. 42 timed sequences for changing the configuration of the watchdog timer ....... 44 interrupts ............................................................................................ 46 interrupt vectors in atmega169......................................................................... 46 i/o-ports.............................................................................................. 51 introduction ......................................................................................................... 51 ports as general digital i/o ................................................................................ 52 alternate port functions ..................................................................................... 56 register description for i/o-ports....................................................................... 73 external interrupts ............................................................................. 76 8-bit timer/counter0 with pwm........................................................ 79 overview............................................................................................................. 79 timer/counter clock sources............................................................................. 80 counter unit........................................................................................................ 80 output compare unit.......................................................................................... 81 compare match output unit ............................................................................... 83 modes of operation ............................................................................................ 84 timer/counter timing diagrams......................................................................... 88 8-bit timer/counter register description ........................................................... 89 timer/counter0 and timer/counter1 prescalers ............................ 93 16-bit timer/counter1 ....................................................................... 95 overview............................................................................................................. 95 accessing 16-bit registers ................................................................................. 98 timer/counter clock sources........................................................................... 101 counter unit...................................................................................................... 101 input capture unit............................................................................................. 102 output compare units ...................................................................................... 104 compare match output unit ............................................................................. 106 modes of operation .......................................................................................... 107 timer/counter timing diagrams....................................................................... 115 16-bit timer/counter register description ....................................................... 117 8-bit timer/counter2 with pwm and asynchronous operation .. 124 overview........................................................................................................... 124 timer/counter clock sources........................................................................... 125 counter unit...................................................................................................... 125 output compare unit........................................................................................ 126 compare match output unit ............................................................................. 128 iii atmega169v/l 2514j?avr?12/03 modes of operation .......................................................................................... 129 timer/counter timing diagrams....................................................................... 133 8-bit timer/counter register description ......................................................... 135 asynchronous operation of the timer/counter ................................................. 138 timer/counter prescaler................................................................................... 142 serial peripheral interface ? spi..................................................... 143 ss pin functionality.......................................................................................... 147 data modes ...................................................................................................... 150 usart .............................................................................................. 151 overview........................................................................................................... 151 clock generation .............................................................................................. 152 frame formats ................................................................................................. 155 usart initialization.......................................................................................... 156 data transmission ? the usart transmitter ................................................. 158 data reception ? the usart receiver .......................................................... 161 asynchronous data reception ......................................................................... 164 multi-processor communication mode ............................................................. 168 usart register description ............................................................................ 169 examples of baud rate setting........................................................................ 174 universal serial interface ? usi...................................................... 178 overview........................................................................................................... 178 functional descriptions .................................................................................... 179 alternative usi usage ...................................................................................... 184 usi register descriptions................................................................................. 184 analog comparator ......................................................................... 189 analog comparator multiplexed input .............................................................. 191 analog to digital converter ............................................................ 192 features............................................................................................................ 192 operation .......................................................................................................... 193 starting a conversion ....................................................................................... 194 prescaling and conversion timing ................................................................... 195 changing channel or reference selection ...................................................... 198 adc noise canceler......................................................................................... 199 adc conversion result.................................................................................... 204 lcd controller ................................................................................. 210 features............................................................................................................ 210 overview........................................................................................................... 210 mode of operation ............................................................................................ 212 lcd usage ....................................................................................................... 216 iv atmega169v/l 2514j?avr?12/03 jtag interface and on-chip debug system ................................. 226 overview........................................................................................................... 226 test access port ? tap.................................................................................... 226 tap controller .................................................................................................. 228 using the boundary-scan chain ....................................................................... 229 using the on-chip debug system .................................................................... 229 on-chip debug specific jtag instructions ...................................................... 230 on-chip debug related register in i/o memory .............................................. 231 using the jtag programming capabilities ...................................................... 231 bibliography ...................................................................................................... 231 ieee 1149.1 (jtag) boundary-scan .............................................. 232 features............................................................................................................ 232 system overview.............................................................................................. 232 data registers .................................................................................................. 232 boundary-scan specific jtag instructions ...................................................... 234 boundary-scan related register in i/o memory .............................................. 236 boundary-scan chain ....................................................................................... 236 atmega169 boundary-scan order................................................................... 246 boundary-scan description language files ..................................................... 251 boot loader support ? read-while-write self-programming ..... 252 boot loader features ....................................................................................... 252 application and boot loader flash sections .................................................... 252 read-while-write and no read-while-write flash sections........................... 252 boot loader lock bits....................................................................................... 255 entering the boot loader program ................................................................... 256 addressing the flash during self-programming .............................................. 258 self-programming the flash ............................................................................. 259 memory programming..................................................................... 266 program and data memory lock bits .............................................................. 266 fuse bits........................................................................................................... 267 signature bytes ................................................................................................ 270 calibration byte ................................................................................................ 270 parallel programming parameters, pin mapping, and commands .................. 270 serial programming pin mapping ..................................................................... 272 parallel programming ....................................................................................... 273 serial downloading........................................................................................... 281 programming via the jtag interface ............................................................... 285 electrical characteristics................................................................ 298 absolute maximum ratings*............................................................................. 298 dc characteristics............................................................................................ 298 external clock drive waveforms ...................................................................... 300 external clock drive ......................................................................................... 300 v atmega169v/l 2514j?avr?12/03 spi timing characteristics ............................................................................... 300 adc characteristics ? preliminary data........................................................... 302 lcd controller characteristics ? preliminary data........................................... 303 atmega169 typical characteristics ? preliminary data .............. 304 register summary ........................................................................... 337 instruction set summary ................................................................ 341 ordering information....................................................................... 344 packaging information .................................................................... 345 64a ................................................................................................................... 345 64m1................................................................................................................. 346 errata ................................................................................................ 347 atmega169 rev d ........................................................................................... 347 atmega169 rev c ........................................................................................... 347 atmega169 rev b ........................................................................................... 348 datasheet change log for atmega169......................................... 350 changes from rev. 2514i-09/03 to rev. 2514j-12/03 ..................................... 350 changes from rev. 2514h-05/03 to rev. 2514i-09/03 .................................... 350 changes from rev. 2514g-04/03 to rev. 2514h-05/03................................... 350 changes from rev. 2514f-04/03 to rev. 2514g-04/03 ................................... 350 changes from rev. 2514e-02/03 to rev. 2514f-04/03 ................................... 350 changes from rev. 2514d-01/03 to rev. 2514e-02/03 ................................... 351 changes from rev. 2514c-11/02 to rev. 2514d-01/03................................... 351 changes from rev. 2514b-09/02 to rev. 2514c-11/02 ................................... 353 changes from rev. 2514a-08/02 to rev. 2514b-09/02 ................................... 353 table of contents ................................................................................. i vi atmega169v/l 2514j?avr?12/03 printed on recycled paper. disclaimer: atmel corporation makes no warranty for the use of its products , other than those expressly contained in the company?s standar d warranty which is detailed in atmel?s terms and conditions located on the company?s web site. the company assumes no responsibi lity for any errors which may appear in this document, reserves the right to change devices or specifications detailed herein at any time wi thout notice, and does not make any commitment to update the information contained herein. no licenses to patents or other intellectual property of atmel are granted by the company in connection with the sale of atmel produc ts, expressly or by implication. atmel?s products are not aut horized for use as critical components in life support devices or systems. atmel corporation atmel operations 2325 orchard parkway san jose, ca 95131, usa tel: 1(408) 441-0311 fax: 1(408) 487-2600 regional headquarters europe atmel sarl route des arsenaux 41 case postale 80 ch-1705 fribourg switzerland tel: (41) 26-426-5555 fax: (41) 26-426-5500 asia room 1219 chinachem golden plaza 77 mody road tsimshatsui east kowloon hong kong tel: (852) 2721-9778 fax: (852) 2722-1369 japan 9f, tonetsu shinkawa bldg. 1-24-8 shinkawa chuo-ku, tokyo 104-0033 japan tel: (81) 3-3523-3551 fax: (81) 3-3523-7581 memory 2325 orchard parkway san jose, ca 95131, usa tel: 1(408) 441-0311 fax: 1(408) 436-4314 microcontrollers 2325 orchard parkway san jose, ca 95131, usa tel: 1(408) 441-0311 fax: 1(408) 436-4314 la chantrerie bp 70602 44306 nantes cedex 3, france tel: (33) 2-40-18-18-18 fax: (33) 2-40-18-19-60 asic/assp/smart cards zone industrielle 13106 rousset cedex, france tel: (33) 4-42-53-60-00 fax: (33) 4-42-53-60-01 1150 east cheyenne mtn. blvd. colorado springs, co 80906, usa tel: 1(719) 576-3300 fax: 1(719) 540-1759 scottish enterprise technology park maxwell building east kilbride g75 0qr, scotland tel: (44) 1355-803-000 fax: (44) 1355-242-743 rf/automotive theresienstrasse 2 postfach 3535 74025 heilbronn, germany tel: (49) 71-31-67-0 fax: (49) 71-31-67-2340 1150 east cheyenne mtn. blvd. colorado springs, co 80906, usa tel: 1(719) 576-3300 fax: 1(719) 540-1759 biometrics/imaging/hi-rel mpu/ high speed converters/rf datacom avenue de rochepleine bp 123 38521 saint-egreve cedex, france tel: (33) 4-76-58-30-00 fax: (33) 4-76-58-34-80 literature requests www.atmel.com/literature 2514j?avr?12/03 ? atmel corporation 2003 . all rights reserved. atmel ? and combinations thereof, avr ? , and avr studio ? are the registered trademarks of atmel corporation or its subsidiaries. microsoft ? , windows ? , windows nt ? , and windows xp ? are the registered trademarks of microsoft corpo- ration. other terms and product names may be the trademarks of others |
Price & Availability of ATMEGA169V-1AI
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |